From: Vivien Kraus <vivien@planete-kraus.eu>
To: Guile User <guile-user@gnu.org>
Subject: Control the order of expansion of syntax-case macros
Date: Tue, 17 Dec 2024 17:33:04 +0100 [thread overview]
Message-ID: <1bfa042ed3719a10006789205e954bb53c83cf45.camel@planete-kraus.eu> (raw)
Dear Guile users,
syntax-case macros can have cool side effects at expansion time.
However, they are still draped in a veil of mystery to me.
Consider this code:
(define-syntax hello
(lambda (stx)
(syntax-case stx ()
(_
(begin
(format (current-error-port) "Hello!\n")
(datum->syntax #f "hello"))))))
(define-syntax world
(lambda (stx)
(syntax-case stx ()
(_
(begin
(format (current-error-port) "World!\n")
(datum->syntax #f "world"))))))
(define-syntax hello-world
(lambda (stx)
(syntax-case stx ()
(_
#`(string-append #,hello " " #,world)))))
,expand hello-world
Running it gives me:
Hello!
World!
$1 = (string-append "hello" " " "world")
Cool! Now, I suspect there are no clear rules to guess the order of
expansion (whether Hello! is printed before World! or after). I would
very much like to twist that order and reliably get World! and then
Hello!. How can I achieve that?
(define-syntax hello-world
(lambda (stx)
(syntax-case stx ()
(_
(let* ((w #'world)
(h #'hello))
#`(string-append #,h " " #,w))))))
With this modification, I get the same order:
Hello!
World!
$1 = (string-append "hello" " " "world")
So my guess is that syntax objects are expanded lazily. Is there
something I can do to get #'world expanded before #'hello?
Best regards,
Vivien
next reply other threads:[~2024-12-17 16:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 16:33 Vivien Kraus [this message]
2024-12-20 9:15 ` Control the order of expansion of syntax-case macros Maxime Devos via General Guile related discussions
2024-12-20 17:01 ` Vivien Kraus
2024-12-20 10:38 ` Nala Ginrut
2024-12-20 20:12 ` Zelphir Kaltstahl
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=1bfa042ed3719a10006789205e954bb53c83cf45.camel@planete-kraus.eu \
--to=vivien@planete-kraus.eu \
--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).