Hello Vivien
On 17.12.24 17:33, Vivien Kraus wrote:
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
I think CK macro style might make it easier/possible, since it is internally
managing a stack of expressions and they compose like usual functions.
It might also be overkill for this specific macro. But if this is not just an
experiment, maybe the actual use case would warrant CK macro style.
Check out the amazing https://okmij.org/ftp/Scheme/macros.html#ck-macros and not
amazing, but perhaps helpful
https://codeberg.org/ZelphirKaltstahl/guile-examples/src/commit/ece4060df673b1a3173856555aeca6d8d8c7fd25/macros/CK-macros/ck-macro.scm
explanations as far as I have once understood what goes on. For a usage example
you could look at
https://codeberg.org/ZelphirKaltstahl/guile-examples/src/commit/ece4060df673b1a3173856555aeca6d8d8c7fd25/macros/contracts.
Once I got my usage of the CK macro right, I found such macro way easier to use
than normal macro which expands from left to right basically (maybe this is not
technically correct to say, I don't know).
Best regards, Zelphir
--
repositories:https://notabug.org/ZelphirKaltstahl,https://codeberg.org/ZelphirKaltstahl