From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 32803@debbugs.gnu.org, tino.calancha@gmail.com
Subject: bug#32803: 26.1.50; cl-do: Add more literature in docstring
Date: Mon, 24 Sep 2018 10:53:04 -0700 [thread overview]
Message-ID: <87d0t2n5of.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <83y3bqal3i.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 24 Sep 2018 19:58:25 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Eric Abrahamsen <eric@ericabrahamsen.net>
>> Cc: Eli Zaretskii <eliz@gnu.org>, 32803@debbugs.gnu.org
>> Date: Mon, 24 Sep 2018 09:43:49 -0700
>>
>> > +Then, in each iteration of the loop, the END-TEST is evaluated; if true,
>> ^^^^^^^
>>
>> >From the peanut gallery: Without looking at the code, I'm not sure if
>> this means the test is evaluated *before* BODY (ie, BODY may never run),
>> or *after* BODY (ie, BODY always runs at least once).
>
> You've removed the answer to that question. The full text says:
>
> Then, in each
> iteration of the loop, the END-TEST is evaluated; if true, the loop
> is finished. Otherwise, the body FORMS are evaluated, then each
> VAR is set to the associated STEP expression [...]
>
> which clearly tells that the test is done _before_ the BODY is run.
> Right?
I guess you're right, yes. "In" still seems unnecessarily vague, though,
when it could simply be replaced with "before". But not that big a deal,
I guess.
next prev parent reply other threads:[~2018-09-24 17:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-22 15:02 bug#32803: 26.1.50; cl-do: Add more literature in docstring Tino Calancha
2018-09-24 9:13 ` Eli Zaretskii
2018-09-24 10:17 ` Tino Calancha
2018-09-24 16:43 ` Eric Abrahamsen
2018-09-24 16:58 ` Eli Zaretskii
2018-09-24 17:53 ` Eric Abrahamsen [this message]
2018-09-24 20:43 ` Tino Calancha
2018-09-27 4:08 ` Eric Abrahamsen
2018-09-28 20:13 ` Tino Calancha
2018-09-28 21:00 ` Eric Abrahamsen
2018-09-29 9:10 ` 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=87d0t2n5of.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=32803@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=tino.calancha@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).