unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Andy Wingo <wingo@igalia.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: (guix modules) and ‘source-module-closure’
Date: Mon, 05 Sep 2016 23:24:12 +0200	[thread overview]
Message-ID: <87twdut4zn.fsf@gnu.org> (raw)
In-Reply-To: <87eg4yzmow.fsf@igalia.com> (Andy Wingo's message of "Mon, 05 Sep 2016 12:05:19 +0200")

Andy Wingo <wingo@igalia.com> skribis:

> On Mon 05 Sep 2016 10:13, Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> writes:
>
>> Ah, very nice!
>>
>> Why is it necessary to read the file and parse the define-module
>> expression?  Does Guile not keep any of this information?  Should it?
>> Will something like this become part of Guile eventually?
>
> If you have the module loaded, there is "live-module-closure" which uses
> the information Guile has at run-time.  I guess Ludovic wanted to get
> this information without loading the module, for some reason :)

Exactly.  Most of the time “build-side” module are not loaded in the
Guile process that uses ‘with-imported-modules’.

It’s a bit of hack but it’s necessary.  Guile could provide this
functionality, but (guix modules) bakes in a few assumptions, notably
that all the source files start with ‘define-module’.

Ludo’.

      reply	other threads:[~2016-09-05 21:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-04 22:24 (guix modules) and ‘source-module-closure’ Ludovic Courtès
2016-09-05  8:13 ` Ricardo Wurmus
2016-09-05 10:05   ` Andy Wingo
2016-09-05 21:24     ` Ludovic Courtès [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://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87twdut4zn.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=wingo@igalia.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).