From: Plamen Tanovski <pgt@tanovski.de>
To: help-gnu-emacs@gnu.org
Subject: Precedence of for clauses in cl-loop
Date: Thu, 06 Sep 2018 20:33:35 +0200 [thread overview]
Message-ID: <20180906183335.ADFDB3381CF@munka.dynalias.org> (raw)
Hi,
the CL info states:
If you include several ‘for’ clauses in a row, they are treated
sequentially (as if by ‘let*’ and ‘setq’).
but in this simple example
(cl-loop for y = x
for x in '(1 2)
for z in '(1 2))
the "for in" clauses are executed before the "for =" clause. Emacs is:
GNU Emacs 27.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.16.7) of
2018-06-08
best regards
--
Plamen Tanovski
next reply other threads:[~2018-09-06 18:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 18:33 Plamen Tanovski [this message]
2018-09-06 22:43 ` Precedence of for clauses in cl-loop Noam Postavsky
2018-09-07 7:08 ` Plamen Tanovski
2018-09-07 11:16 ` Noam Postavsky
2018-09-07 12:35 ` Plamen Tanovski
2018-09-08 1:37 ` Noam Postavsky
[not found] ` <mailman.511.1536370625.1284.help-gnu-emacs@gnu.org>
2018-09-08 14:41 ` Udyant Wig
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=20180906183335.ADFDB3381CF@munka.dynalias.org \
--to=pgt@tanovski.de \
--cc=help-gnu-emacs@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.
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).