From: Vivien Kraus <vivien@planete-kraus.eu>
To: Maxime Devos <maximedevos@telenet.be>,
"guile-user@gnu.org" <guile-user@gnu.org>
Subject: Re: Dynamically add bindings to the module currently being compiled
Date: Sat, 09 Nov 2024 23:05:07 +0100 [thread overview]
Message-ID: <49519a93570f4fb33ba26897f2c34befc7f89ef1.camel@planete-kraus.eu> (raw)
In-Reply-To: <63c53bc333cc0f261fe213cbea21978828ec3592.camel@planete-kraus.eu>
Le samedi 09 novembre 2024 à 22:57 +0100, Vivien Kraus a écrit :
> With your precious help and some digging around, I produced the
> attached code. Thank you!
P.S. I am a bit perplexed by syntax-parameterize introducing (let () …)
forms in the expansion but I think I can work around it by doing
define-public instead of define.
prev parent reply other threads:[~2024-11-09 22:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-09 12:27 Dynamically add bindings to the module currently being compiled Vivien Kraus
2024-11-09 13:06 ` Maxime Devos via General Guile related discussions
2024-11-09 21:57 ` Vivien Kraus
2024-11-09 22:05 ` Vivien Kraus [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=49519a93570f4fb33ba26897f2c34befc7f89ef1.camel@planete-kraus.eu \
--to=vivien@planete-kraus.eu \
--cc=guile-user@gnu.org \
--cc=maximedevos@telenet.be \
/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).