unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: prj@case.edu (Paul Jarc)
To: guile-user@gnu.org
Subject: Re: defining macros within eval
Date: Wed, 19 Oct 2022 04:42:43 -0400	[thread overview]
Message-ID: <ozkd1qr48arg.fsf@webapps-d-2.tis.cwru.edu> (raw)
In-Reply-To: <3c0dd8aa-97cb-9b31-9e93-44a93ed59a6a@telenet.be> (Maxime Devos's message of "Sun, 16 Oct 2022 18:17:27 +0200")

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?

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.  It's similar to
include in that way, but the loaded code goes into its own module and
only certain bindings are imported, as with :select from use-modules.
Each file is loaded only once per run, and typically doesn't change
between runs, so somehow it ought to work with compilation enabled.

I'll try playing around with include, eval-when, and datum->syntax to
see if I can get something working, but if the extra context brings
anything else to mind, more suggestions are welcome too.  This feels
like it would be trivial if the module system had a little more of its
guts exposed.



  reply	other threads:[~2022-10-19  8:42 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 [this message]
2022-10-19 17:36     ` Maxime Devos

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=ozkd1qr48arg.fsf@webapps-d-2.tis.cwru.edu \
    --to=prj@case.edu \
    --cc=guile-user@gnu.org \
    /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).