From: Stefan Monnier <monnier@iro.umontreal.ca>
To: help-gnu-emacs@gnu.org
Subject: Re: Elisps rplacd vs CL's one
Date: Sat, 29 Aug 2015 18:05:04 -0400 [thread overview]
Message-ID: <jwvy4gtu4xz.fsf-monnier+gmane.emacs.help@gnu.org> (raw)
In-Reply-To: 87oahqlgpo.fsf@mbork.pl
> Emacs Lisp's rplacd and Common Lisp's RPLACD are called the same, but
> behave differently (ELisp's one returns the NEWCDR and CL's one returns
> the modified cons). What is the reason for that? Is it an accident?
> While I do understand that EL ≠ CL, having a function called the same in
> both, doing roughly the same thing, but not quite, seems a bit
> misleading, and I was just curious whether there was a deep reason for
> that.
FWIW, I consider the use of rplacd's return value to be a very bad idea.
Stefan
next prev parent reply other threads:[~2015-08-29 22:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-29 7:02 Elisps rplacd vs CL's one Marcin Borkowski
2015-08-29 22:05 ` Stefan Monnier [this message]
2015-08-30 4:51 ` Marcin Borkowski
[not found] <mailman.120.1440831791.19560.help-gnu-emacs@gnu.org>
2015-08-29 8:01 ` Pascal J. Bourguignon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvy4gtu4xz.fsf-monnier+gmane.emacs.help@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).