unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: sokobania.01@gmail.com, help-gnu-emacs@gnu.org
Subject: RE: Always using let*
Date: Tue, 16 Sep 2014 09:41:09 -0700 (PDT)	[thread overview]
Message-ID: <c13ab9a1-32fb-4aed-8ffb-1e31fe4aac9e@default> (raw)
In-Reply-To: <732966c5-a667-4fc7-9d07-8da315862ce2@googlegroups.com>

> > In sum: If I use `let*' then look for a binding dependency.
> >         If I use `let'  then don't bother to look for one.
> 
> I agree.
> 
> Some cases are intermediate.  If I have several variables with "enough"
> binding dependency, I use "let*".
> 
> But, quite often, I have several independent variable, except one or
> two. So, I would use "let" rather than "let*", but don't bind these
> variables and then use "setq" in the body of the let:
>
> (let ((a (val-for-a))
>       (b (val-for-b))
>       ...
>       x y) ; depend on a b
>    (setq x (val-for-x a b))
>    (setq y (val-for-y a b))
>    ...)

Yup.  Me too.  Especially if any processing needs to be done
after the bindings and before the assignments (setq).



  reply	other threads:[~2014-09-16 16:41 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-14 19:46 Always using let* Cecil Westerhof
2014-09-14 21:25 ` Drew Adams
2014-09-15 16:15   ` Drew Adams
     [not found]   ` <mailman.8924.1410797740.1147.help-gnu-emacs@gnu.org>
2014-09-15 18:01     ` Cecil Westerhof
2014-09-15 22:20       ` Emanuel Berg
2014-09-16 12:05         ` Cecil Westerhof
2014-09-16 22:40           ` Emanuel Berg
2014-09-18 17:02             ` Cecil Westerhof
2014-09-18 21:05               ` Emanuel Berg
2014-09-16 14:23     ` sokobania.01
2014-09-16 16:41       ` Drew Adams [this message]
2014-09-16 20:49       ` Stefan Monnier
2014-09-16 22:45       ` Emanuel Berg
     [not found]       ` <mailman.8998.1410901776.1147.help-gnu-emacs@gnu.org>
2014-09-16 22:48         ` Emanuel Berg
2014-09-17  1:09           ` Stefan Monnier
2014-09-17  1:18             ` Emanuel Berg
2014-09-14 21:40 ` Joe Fineman
     [not found] ` <mailman.8868.1410729956.1147.help-gnu-emacs@gnu.org>
2014-09-14 21:41   ` Emanuel Berg
2014-09-14 22:11   ` Cecil Westerhof
2014-09-14 22:56     ` Drew Adams
2014-09-14 22:41   ` Stefan Monnier
2014-09-14 23:06     ` Drew Adams
     [not found]     ` <mailman.8871.1410736002.1147.help-gnu-emacs@gnu.org>
2014-09-15  0:47       ` Emanuel Berg
2014-09-15  2:12         ` Pascal J. Bourguignon
2014-09-15  2:22       ` Stefan Monnier
2014-09-15  2:59         ` Pascal J. Bourguignon
2014-09-15 12:31           ` Stefan Monnier
2014-09-15 16:15             ` Drew Adams
2014-09-15 19:05               ` Stefan Monnier
     [not found]               ` <mailman.8930.1410808006.1147.help-gnu-emacs@gnu.org>
2014-09-15 22:28                 ` Emanuel Berg
2014-09-16  0:38                   ` Pascal J. Bourguignon
2014-09-15 13:14           ` Barry Margolin

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=c13ab9a1-32fb-4aed-8ffb-1e31fe4aac9e@default \
    --to=drew.adams@oracle.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=sokobania.01@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.
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).