unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Marcin Borkowski <mbork@mbork.pl>
To: help-gnu-emacs@gnu.org
Subject: Re: Elisps rplacd vs CL's one
Date: Sun, 30 Aug 2015 06:51:37 +0200	[thread overview]
Message-ID: <87twrhml9i.fsf@mbork.pl> (raw)
In-Reply-To: <jwvy4gtu4xz.fsf-monnier+gmane.emacs.help@gnu.org>


On 2015-08-30, at 00:05, Stefan Monnier <monnier@iro.umontreal.ca> wrote:

> FWIW, I consider the use of rplacd's return value to be a very bad idea.

I stumbled on it while studying the implementation of APPEND in CCL
(sent to the list by Pascal some time ago).

>         Stefan

Best,

-- 
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University



  reply	other threads:[~2015-08-30  4:51 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
2015-08-30  4:51   ` Marcin Borkowski [this message]
     [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=87twrhml9i.fsf@mbork.pl \
    --to=mbork@mbork.pl \
    --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).