From: npostavs@users.sourceforge.net
To: Alex <agrambot@gmail.com>
Cc: 25154@debbugs.gnu.org
Subject: bug#25154: 25.1; Bindings in cl-letf are in reverse order
Date: Sat, 10 Dec 2016 13:14:54 -0500 [thread overview]
Message-ID: <87bmwjejmp.fsf@users.sourceforge.net> (raw)
In-Reply-To: <87bmwjy80b.fsf@gmail.com> (Alex's message of "Sat, 10 Dec 2016 12:05:40 -0600")
Alex <agrambot@gmail.com> writes:
>>
>> Isn't it true that the order of evaluation in a 'let' is unspecified?
>> If you want a particular order, use 'let*'.
>
> I don't think so. See (info "(elisp) Local Variables"):
>
> All of the VALUE-FORMs in BINDINGS are evaluated in the order they
> appear
>
> I believe it should follow for cl-letf. Besides, even if it was
> unspecified, evaluating in the order they appear would be adhering to
> the principle of least astonishment.
The value forms are evaluated in order, the bindings are not necessarily
in order.
(let ((x 0))
(cl-letf ((a (setq x 1))
(a (setq x 2)))
(list x a))) ;=> (2 1)
Although `let' does happen to perform the bindings in order too.
(let ((x 0))
(let ((a (setq x 1))
(a (setq x 2)))
(list x a))) ;=> (2 2)
next prev parent reply other threads:[~2016-12-10 18:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-09 23:36 bug#25154: 25.1; Bindings in cl-letf are in reverse order Alex
2016-12-10 4:29 ` Alex
2016-12-10 7:22 ` Eli Zaretskii
2016-12-10 7:43 ` Tino Calancha
2016-12-10 13:41 ` Philipp Stephani
2016-12-10 14:01 ` Tino Calancha
2016-12-10 14:09 ` Eli Zaretskii
2016-12-23 12:17 ` Philipp Stephani
2016-12-23 12:46 ` Tino Calancha
2016-12-23 13:53 ` Eli Zaretskii
2016-12-23 16:30 ` Philipp Stephani
2016-12-10 18:05 ` Alex
2016-12-10 18:14 ` npostavs [this message]
2016-12-10 19:41 ` Alex
2016-12-10 18:27 ` Eli Zaretskii
2016-12-10 19:52 ` Alex
2016-12-11 3:11 ` Tino Calancha
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=87bmwjejmp.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=25154@debbugs.gnu.org \
--cc=agrambot@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).