unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Oleh Krehel <ohwoeowho@gmail.com>, Alan Mackenzie <acm@muc.de>
Cc: emacs-devel@gnu.org
Subject: multi-assignment setq    [was: setq's with missing final arguments.]
Date: Sun, 22 Nov 2015 07:53:52 -0800 (PST)	[thread overview]
Message-ID: <b43034dc-02e5-48f7-8175-1137c1941784@default> (raw)
In-Reply-To: <87si3yp5y6.fsf@gmail.com>

> In my opinion, multi-variable setq should be deprecated altogether.

(This is a change of topic.  The Subject line should change too.)

Presumably, since `setq' can make multiple assignments to the
same variable, you mean not "multi-variable" but "multi-assignment".

> I'm sure many people will disagree for the reasons of habit,

I disagree completely.  But not out of habit.  In fact, for
years (quite a long time, in fact) I avoided it, in favor of
multiple `setq' calls.  If necessary, I can give the reasons
why I now prefer to use a single `setq' with multiple assignments.

> but multi-variable setq is just plain bad: it makes LISP less
> lispy that it should be. For example: "(setq bar)" is a nice
> sexp: you can delete it, copy it, comment it, move it around

That quality is not what I consider "lispiness".  That same
complaint applies to `let*' and a zillion other Lisp veterans.



  parent reply	other threads:[~2015-11-22 15:53 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-22 12:26 setq's with missing final arguments Alan Mackenzie
2015-11-22 12:31 ` David Kastrup
2015-11-22 12:35 ` Oleh Krehel
2015-11-22 12:44   ` Teemu Likonen
2015-11-22 15:53   ` Drew Adams [this message]
2015-11-23  7:58     ` multi-assignment setq [was: setq's with missing final arguments.] Oleh Krehel
2015-11-23 15:02       ` Drew Adams
2015-11-22 12:52 ` setq's with missing final arguments Andreas Schwab
2015-11-22 13:03   ` Artur Malabarba
2015-11-22 13:08   ` David Kastrup
2015-11-22 13:11     ` Andreas Schwab
2015-11-22 13:23       ` David Kastrup
2015-11-22 13:34         ` Andreas Schwab
2015-11-22 14:10           ` Alan Mackenzie
2015-11-22 15:44             ` Eli Zaretskii
2015-11-22 19:44               ` Alan Mackenzie
2015-11-23  1:36                 ` Drew Adams
2015-11-22 15:42 ` Johan Bockgård
2015-11-22 16:04   ` Drew Adams
2015-11-22 15:52 ` Drew Adams
2015-11-22 23:08   ` Alan Mackenzie
2015-11-22 23:20     ` John Wiegley
2015-11-23  1:54       ` 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=b43034dc-02e5-48f7-8175-1137c1941784@default \
    --to=drew.adams@oracle.com \
    --cc=acm@muc.de \
    --cc=emacs-devel@gnu.org \
    --cc=ohwoeowho@gmail.com \
    /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).