From: Maxime Devos <maximedevos@telenet.be>
To: Paul Jarc <prj@case.edu>, guile-user@gnu.org
Subject: Re: defining macros within eval
Date: Wed, 19 Oct 2022 19:36:13 +0200 [thread overview]
Message-ID: <0e870b9c-6909-7ad2-ded7-aa91464e14df@telenet.be> (raw)
In-Reply-To: <ozkd1qr48arg.fsf@webapps-d-2.tis.cwru.edu>
[-- Attachment #1.1.1: Type: text/plain, Size: 868 bytes --]
On 19-10-2022 10:42, Paul Jarc wrote:
> Maxime Devos <maximedevos@telenet.be> wrote:
>> For an example in the wild, see
>> e.g. <https://git.gnunet.org/gnunet-scheme.git/tree/gnu/gnunet/message/protocols.scm>.
>
> Thanks (to Jean as well) for all the suggestions. Can you point me to
> an example of where include/sexp is used?
It is used by protocols.scmgen (which is included by protocols.scm) --
protocols.scm and protocols.scmgen form a pair, you'll have to read both
of them.
> To take a step back, my ultimate goal is to have a separate module
> system, where code libraries are identified by their full pathname
> rather than an abstract name applied to %load-path. [...]
'load-compiled' (if you compile things separately) or 'load' otherwise
may be useful, they accept file names instead of module names.
Greetings,
Maxime.
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
prev parent reply other threads:[~2022-10-19 17:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-16 9:39 defining macros within eval Paul Jarc
2022-10-16 14:07 ` Jean Abou Samra
2022-10-16 16:21 ` Maxime Devos
2022-10-16 16:13 ` Maxime Devos
2022-10-16 16:17 ` Maxime Devos
2022-10-19 8:42 ` Paul Jarc
2022-10-19 17:36 ` Maxime Devos [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=0e870b9c-6909-7ad2-ded7-aa91464e14df@telenet.be \
--to=maximedevos@telenet.be \
--cc=guile-user@gnu.org \
--cc=prj@case.edu \
/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).