From: Tino Calancha <tino.calancha@gmail.com>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: 25154@debbugs.gnu.org, Alex <agrambot@gmail.com>,
Tino Calancha <tino.calancha@gmail.com>
Subject: bug#25154: 25.1; Bindings in cl-letf are in reverse order
Date: Sat, 10 Dec 2016 23:01:55 +0900 (JST) [thread overview]
Message-ID: <alpine.DEB.2.20.1612102257490.22291@calancha-pc> (raw)
In-Reply-To: <CAArVCkRujHGKQQJrZwc_raCxRCnPS73g4i7f0=S-0n0_uxH=9Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 679 bytes --]
On Sat, 10 Dec 2016, Philipp Stephani wrote:
>
>
> Tino Calancha <tino.calancha@gmail.com> schrieb am Sa., 10. Dez. 2016 um 08:45 Uhr:
> Eli Zaretskii <eliz@gnu.org> writes:
>
> Right, the order of evaluation in a let is up to the implementation. A program
> should not rely on such details.
> The same statement should apply to cl-letf.
Sorry, i meant above
the order of 'assign the bindings' is up to the implementation.
> I think that should be mentioned explicitly in the manuals: given that the order of value evaluations is specified, people might
> expect the same for the bindings themselves.
Yes, it's worth to remark than in the manual.
next prev parent reply other threads:[~2016-12-10 14:01 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 [this message]
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
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=alpine.DEB.2.20.1612102257490.22291@calancha-pc \
--to=tino.calancha@gmail.com \
--cc=25154@debbugs.gnu.org \
--cc=agrambot@gmail.com \
--cc=p.stephani2@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).