From: Andreas Reuleaux <rx@a-rx.info>
To: Damien Mattei <damien.mattei@gmail.com>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: unusual let binding (of lp) - in function element->xml from sxml simple
Date: Sun, 04 Feb 2024 15:37:46 +0000 [thread overview]
Message-ID: <87y1c09r5h.fsf@softland> (raw)
In-Reply-To: <CADEOadft4V4yf5xnGfY1sezx+QcujRcjbFUQszVPaCg=foK8ng@mail.gmail.com> (Damien Mattei's message of "Sun, 4 Feb 2024 09:46:24 +0100")
Hi, and thanks to you, too.
-Andreas
Damien Mattei <damien.mattei@gmail.com> writes:
> Hi Andreas,
> a good explanation is here:
> https://stackoverflow.com/questions/31909121/how-does-the-named-let-in-the-form-of-a-loop-work
> personally i avoid to use it, as i can do the same with internal
> definitions .
> regards,
> Damien
>
prev parent reply other threads:[~2024-02-04 15:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-03 21:51 unusual let binding (of lp) - in function element->xml from sxml simple Andreas Reuleaux
2024-02-03 21:55 ` Thompson, David
2024-02-03 22:16 ` Andreas Reuleaux
2024-02-04 6:30 ` tomas
2024-02-04 8:46 ` Damien Mattei
2024-02-04 15:37 ` Andreas Reuleaux [this message]
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y1c09r5h.fsf@softland \
--to=rx@a-rx.info \
--cc=damien.mattei@gmail.com \
--cc=guile-user@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).