From: Eli Zaretskii <eliz@gnu.org>
To: arthur miller <arthur.miller@live.com>
Cc: ams@gnu.org, yuri.v.khan@gmail.com, emacs-devel@gnu.org
Subject: Re: Is this a bug in while-let or do I missunderstand it?
Date: Sun, 10 Nov 2024 08:22:17 +0200 [thread overview]
Message-ID: <86ldxrliau.fsf@gnu.org> (raw)
In-Reply-To: <DU2PR02MB101096BE38E4809D2FC01C192965E2@DU2PR02MB10109.eurprd02.prod.outlook.com> (message from arthur miller on Sat, 9 Nov 2024 20:29:29 +0000)
> From: arthur miller <arthur.miller@live.com>
> CC: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
> Date: Sat, 9 Nov 2024 20:29:29 +0000
>
> In other words, there might be variables live outisde of
> the loop-scope we wish to access in the loop, and that is
> what Yuri's example shows. However, i,j are not re-initiated
> on each iteration, but remembers their value. The effecto of
> while-let in current implementation is that i,j are re-initiated
> in each iteration, not re-evaluated, if that makes it clear.
>
> I am not sure how to illustrate in a better way. The net effect is
> that lexical variables declared in while-let loop are "read-only".
>
> They are not, but since they are re-iniated, it is pointless to
> write to them.
You can write to them indirectly, if the evaluation is properly
written. If the evaluation is just assigning a fixed value to a
variable, then yes, writing to that variable in the body is pointless;
but then so is the use of while-let, IMO.
Even in your for-loop example from C, the CONDITION part of the loop
is re-evaluated on each iteration, and if you assign some fixed value
to the loop control variables there, your loop might become an
infloop, regardless of what you do in the body with those variables.
That's basically what the example of while-let you show at the
beginning of this discussion did.
> Of course, all loop predicates should be evaled on each iteration,
> but not re-iniated on each iteration. If that makes sense. Sorry,
> I am not very good at writing.
If while-let doesn't seem to do the job in some code of yours, then
don't use it there. Use something else. AFAIU, while-let was
introduced for those cases where its use makes sense and does the job
cleaner and clearer than the alternatives. It could be abused, of
course, but that's not necessarily its fault, is it?
Anyway, to get this long discussion back on track: is there a need to
clarify something in the documentation of while-let? if so, what?
next prev parent reply other threads:[~2024-11-10 6:22 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 16:25 Is this a bug in while-let or do I missunderstand it? arthur miller
2024-11-08 19:23 ` Philip Kaludercic
2024-11-09 3:30 ` Sv: " arthur miller
2024-11-09 9:29 ` Yuri Khan
2024-11-09 13:03 ` Sv: " arthur miller
2024-11-09 13:15 ` Yuri Khan
2024-11-09 13:38 ` Sv: " arthur miller
2024-11-09 13:41 ` Yuri Khan
2024-11-09 13:47 ` Sv: " arthur miller
2024-11-09 14:04 ` Yuri Khan
2024-11-09 14:44 ` Sv: " arthur miller
2024-11-09 16:33 ` Alfred M. Szmidt
2024-11-09 16:44 ` Eli Zaretskii
2024-11-09 16:53 ` Eli Zaretskii
2024-11-09 17:33 ` Andreas Schwab
2024-11-09 18:07 ` [External] : " Drew Adams
2024-11-09 18:18 ` Alfred M. Szmidt
2024-11-09 20:02 ` Jens Schmidt
2024-11-09 20:38 ` Alfred M. Szmidt
2024-11-09 21:18 ` Joost Kremers
2024-11-10 11:44 ` Alfred M. Szmidt
2024-11-10 12:24 ` Better documentation for non-binding clauses of if-let and friends Jens Schmidt
2024-11-10 14:51 ` Sean Whitton
2024-11-10 16:58 ` Jens Schmidt
2024-11-11 10:03 ` Alfred M. Szmidt
2024-11-11 8:20 ` Alfred M. Szmidt
2024-11-09 19:32 ` Sv: [External] : Re: Is this a bug in while-let or do I missunderstand it? arthur miller
2024-11-09 22:36 ` Drew Adams
2024-11-09 22:53 ` Drew Adams
2024-11-14 21:50 ` John ff
2024-11-09 20:29 ` Sv: " arthur miller
2024-11-10 6:22 ` Eli Zaretskii [this message]
2024-11-10 10:40 ` Joost Kremers
2024-11-10 12:10 ` Alfred M. Szmidt
2024-11-10 19:49 ` Sv: " arthur miller
2024-11-10 18:18 ` arthur miller
2024-11-11 5:13 ` Yuri Khan
2024-11-11 8:49 ` Sv: " arthur miller
2024-11-11 12:23 ` tomas
2024-11-11 22:41 ` Joost Kremers
2024-11-12 12:19 ` Eli Zaretskii
2024-11-12 12:45 ` Joost Kremers
2024-11-12 14:34 ` Eli Zaretskii
2024-11-12 15:32 ` Joost Kremers
2024-11-12 23:45 ` Joost Kremers
2024-11-13 9:45 ` Sean Whitton
2024-11-13 9:56 ` Sean Whitton
2024-11-13 11:00 ` Joost Kremers
2024-11-13 12:17 ` Sean Whitton
2024-11-14 7:55 ` Eli Zaretskii
2024-11-14 8:21 ` Joost Kremers
2024-11-14 21:51 ` John ff
2024-11-14 21:52 ` John ff
2024-11-09 21:47 ` Sv: " Joost Kremers
2024-11-09 22:07 ` Sv: " arthur miller
2024-11-10 6:07 ` Andreas Schwab
-- strict thread matches above, loose matches on Subject: below --
2024-11-12 3:36 arthur miller
2024-11-12 8:30 ` Joost Kremers
2024-11-12 17:55 ` Alfred M. Szmidt
2024-11-12 3:41 arthur miller
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=86ldxrliau.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=ams@gnu.org \
--cc=arthur.miller@live.com \
--cc=emacs-devel@gnu.org \
--cc=yuri.v.khan@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).