From: Han-Wen Nienhuys <hanwenn@gmail.com>
To: "Linus Björnstam" <linus.bjornstam@veryfast.biz>
Cc: guile-devel@gnu.org
Subject: Re: unhandled constant?
Date: Fri, 31 Jan 2020 16:16:46 +0100 [thread overview]
Message-ID: <CAOw_e7aEUGaH01BabiSJxQJVnjDF3OLLoYkuNbjtREJLghAEqg@mail.gmail.com> (raw)
In-Reply-To: <8d77f905-31e9-4d0b-973a-82be38360e07@www.fastmail.com>
On Fri, Jan 31, 2020 at 3:58 PM Linus Björnstam
<linus.bjornstam@veryfast.biz> wrote:
>
> Guile1.8's macros are run-time macros: they are executed directly and not transformed to output code that is then compiled. That is the reason why your code works: to newer guiles the (inner ...) is only available at expansion time. The macro output is trying to call code that does not exist at runtime!
>
> For this to be working code the (inner ...) function needs to be available in the macro expansion. I didn't read through exactly what you are trying to do, but try outputting a let:
>
> `(let ((inner (lambda (n v) (set ! ...))))
> (inner ,name ,value))
>
> I doubt you can make the old code work in newer guiles, since I doubt any scheme is a s lax about expansion time and macro time separation.
Thanks for the explanation. This makes sense.
Is it possible to attach doc strings to (define-syntax .. )
declarations, and if so, where do they go?
--
Han-Wen Nienhuys - hanwenn@gmail.com - http://www.xs4all.nl/~hanwen
next prev parent reply other threads:[~2020-01-31 15:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 23:08 unhandled constant? Han-Wen Nienhuys
2020-01-29 15:06 ` Ricardo Wurmus
2020-01-30 8:05 ` Han-Wen Nienhuys
2020-01-31 10:49 ` Han-Wen Nienhuys
2020-01-31 11:17 ` Ricardo Wurmus
2020-02-02 19:30 ` Jan Nieuwenhuizen
2020-01-31 14:57 ` Linus Björnstam
2020-01-31 15:16 ` Han-Wen Nienhuys [this message]
2020-01-31 17:50 ` Han-Wen Nienhuys
2020-01-31 18:19 ` Linus Björnstam
2020-01-31 19:17 ` Han-Wen Nienhuys
2020-01-31 19:52 ` Linus Björnstam
2020-01-31 20:01 ` Linus Björnstam
2020-02-01 9:54 ` Han-Wen Nienhuys
2020-02-01 9:56 ` Han-Wen Nienhuys
2020-02-01 10:10 ` David Kastrup
2020-02-01 11:23 ` Han-Wen Nienhuys
2020-02-01 11:36 ` David Kastrup
2020-02-01 13:12 ` Linus Björnstam
2020-02-01 11:09 ` David Kastrup
2020-02-01 13:16 ` Linus Björnstam
2020-02-01 14:23 ` David Kastrup
2020-02-01 15:21 ` Linus Björnstam
2020-02-01 21:55 ` Taylan Kammer
2020-02-01 21:58 ` Fwd: " Taylan Kammer
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=CAOw_e7aEUGaH01BabiSJxQJVnjDF3OLLoYkuNbjtREJLghAEqg@mail.gmail.com \
--to=hanwenn@gmail.com \
--cc=guile-devel@gnu.org \
--cc=linus.bjornstam@veryfast.biz \
/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).