From: Jean Abou Samra <jean@abou-samra.fr>
To: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
Cc: Walter Lewis <wklew@mailbox.org>, guile-user@gnu.org
Subject: Re: Breaking hygiene with syntax-rules?
Date: Sat, 12 Aug 2023 01:57:42 +0200 [thread overview]
Message-ID: <e80b775af57b88f6319f4dff47faccc32d08b7e4.camel@abou-samra.fr> (raw)
In-Reply-To: <87y1iiynzy.fsf@web.de>
[-- Attachment #1: Type: text/plain, Size: 991 bytes --]
Le vendredi 11 août 2023 à 10:33 +0200, Dr. Arne Babenhauserheide a écrit :
>
> Jean Abou Samra <jean@abou-samra.fr> writes:
>
> > This is a known limitation in Guile. Please read
> > https://www.gnu.org/software/guile/manual/html_node/Hygiene-and-the-Top_002dLevel.html
>
> I would not expect that effect from the description, because in
>
> (define-syntax unhygienic
> (syntax-rules ()
> ((_ the-pair fetch)
> (begin
> (define the-head (car the-pair))
> (define (the-proc) the-head)
> (define (fetch) the-head)))))
>
> the-head depends on (car the-pair) and the-pair is a variable passed to
> the macro. So I would expect this to create different identifiers for
> different values of the-pair, just like it creates different identifiers
> when instead of (car the-pair) I use fetch (also passed from outside).
You're right, that's confusing.
I don't have the time to investigate, though.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-08-11 23:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 2:35 Breaking hygiene with syntax-rules? Walter Lewis via General Guile related discussions
2023-08-11 5:07 ` Dr. Arne Babenhauserheide
2023-08-11 8:00 ` Jean Abou Samra
2023-08-11 8:33 ` Dr. Arne Babenhauserheide
2023-08-11 23:57 ` Jean Abou Samra [this message]
2023-08-12 5:57 ` Dr. Arne Babenhauserheide
2023-08-11 13:34 ` Walter Lewis via General Guile related discussions
2023-08-11 22:50 ` Walter Lewis via General Guile related discussions
2023-08-11 23:55 ` Jean Abou Samra
2023-08-11 23:57 ` Jean Abou Samra
2023-08-12 0:19 ` Walter Lewis
2023-08-12 0:58 ` Jean Abou Samra
2023-08-12 5:59 ` Dr. Arne Babenhauserheide
2023-08-14 19:26 ` Thompson, David
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=e80b775af57b88f6319f4dff47faccc32d08b7e4.camel@abou-samra.fr \
--to=jean@abou-samra.fr \
--cc=arne_bab@web.de \
--cc=guile-user@gnu.org \
--cc=wklew@mailbox.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).