On 19-10-2022 10:42, Paul Jarc wrote:
Maxime Devos <maximede...@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: OpenPGP_0x49E3EE22191725EE.asc
Description: OpenPGP public key

Attachment: OpenPGP_signature
Description: OpenPGP digital signature

Reply via email to