From: Drew Adams <drew.adams@oracle.com>
To: Jordon Biondo <jordonbiondo@gmail.com>, rms@gnu.org
Cc: Stefan Monnier <monnier@IRO.UMontreal.CA>, emacs-devel@gnu.org
Subject: RE: giving `setq-local' the same signature as `setq'
Date: Thu, 19 Mar 2015 08:11:41 -0700 (PDT) [thread overview]
Message-ID: <0471cc2e-84d4-4a15-88b6-92a980e2949e@default> (raw)
In-Reply-To: <A13B39EF-9AD1-4B96-94DA-D731C41AABB1@gmail.com>
> > > I find this behavior of `setq' to be a misfeature, which is
> > > why I haven't adopted it for setq-local.
>
> > It is most natural for setq-local to have the same calling
> > convention as setq.
>
> I understand the notion of setq's signature being a misfeature,
You do? Pray tell, in what way is it a misfeature? Nothing has
been said to elucidate this, so far - it has only been asserted.
IMHO, it is a feature, giving users the choice. Just like implicit
`progn' gives you the choice of adding `progn' or not.
I often prefer to see sequential assignments grouped in the same
`setq'. It means a lot less noise, for one thing.
Especially when it means not needing to group multiple `setq's
using `progn'.
> but seeing as that will never change, I would tend to think that
> `setq-local’ should reflect it’s name and act the same as `setq’
Yes. Not to mention the same as Common Lisp `setf' and `psetf'...
(Other Lisps too.)
> but change values locally.
Yes, I think so too, FWIW.
next prev parent reply other threads:[~2015-03-19 15:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 15:26 giving `setq-local' the same signature as `setq' Jordon Biondo
2015-03-18 16:24 ` Stefan Monnier
2015-03-19 14:08 ` Richard Stallman
2015-03-19 14:48 ` Jordon Biondo
2015-03-19 15:11 ` Drew Adams [this message]
2015-03-19 15:17 ` Oleh Krehel
2015-03-19 15:39 ` Drew Adams
2015-03-19 15:55 ` Oleh Krehel
2015-03-19 17:25 ` Drew Adams
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=0471cc2e-84d4-4a15-88b6-92a980e2949e@default \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=jordonbiondo@gmail.com \
--cc=monnier@IRO.UMontreal.CA \
--cc=rms@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).