From: spacecadet <spacecadet@purge.sh>
To: Maxime Devos <maximedevos@telenet.be>,
Taylan Kammer <taylan.kammer@gmail.com>,
"guile-devel@gnu.org" <guile-devel@gnu.org>
Subject: Re: Lexically bound macro, with lexically bound transformer
Date: Sat, 27 Jul 2024 00:30:20 +0000 [thread overview]
Message-ID: <c8b64ad4-b797-4fb0-2ee8-ce7583126af7@purge.sh> (raw)
In-Reply-To: <20240726095655.s7wu2C00U2kuPDg017wuaE@baptiste.telenet-ops.be>
> The question is: why would you do that?
Why not? :)
I'm trying to create a functional module system (similar to nixpkgs/nixos),
where modules are functions, imports are arguments, and exports are just the
return of the function.
Seems like scheme macros can't really work like that, although the suggestions
have given me a lot of help. Thank you.
prev parent reply other threads:[~2024-07-27 0:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-24 1:06 Lexically bound macro, with lexically bound transformer spacecadet
2024-07-24 11:15 ` Taylan Kammer
2024-07-24 17:10 ` spacecadet
2024-07-24 19:54 ` Attila Lendvai
2024-07-25 9:50 ` Taylan Kammer
2024-07-26 7:56 ` Maxime Devos
2024-07-27 0:30 ` spacecadet [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=c8b64ad4-b797-4fb0-2ee8-ce7583126af7@purge.sh \
--to=spacecadet@purge.sh \
--cc=guile-devel@gnu.org \
--cc=maximedevos@telenet.be \
--cc=taylan.kammer@gmail.com \
/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).