From: "Jose A. Ortega Ruiz" <jao@gnu.org>
To: guile-devel@gnu.org
Subject: Re: [PATCH] Fix for `submodules' in (ice-9 session) (closes #30062)
Date: Wed, 01 Sep 2010 22:58:03 +0200 [thread overview]
Message-ID: <87y6blyyec.fsf@newton.homeunix.net> (raw)
In-Reply-To: 877hj5r7rt.fsf@gnu.org
On Wed, Sep 01 2010, Ludovic Courtès wrote:
> Hi!
>
> "Jose A. Ortega Ruiz" <jao@gnu.org> writes:
>
>> (I'm still curious about the meaning of the
>> modules with gensyms as names, though.)
>
> psyntax expects modules to have a name so that it can refer to them in
> expanded code. Thus, there can be no anonymous modules: modules are
> always given a name, see ‘module-name’. This allows things like the
> “compile in fresh module” test to work.
I see. But then, aren't those modules something internal to psyntax's
workings? And if so, shouldn't they be filtered out from the return
value of module-submodules (or not be traversed by the apropos-fold)? As
a user of those procedures, i find the appearance of those modules a bit
confusing (the only use case in client code i can think of is when using
the return value of current-module). Am i missing something?
Thanks,
jao
--
Nature uses as little as possible of anything.
-Johannes Kepler, astronomer (1571-1630)
next prev parent reply other threads:[~2010-09-01 20:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-31 12:19 [PATCH] Fix for `submodules' in (ice-9 session) (closes #30062) Jose A. Ortega Ruiz
2010-08-31 16:04 ` Andy Wingo
2010-08-31 20:29 ` Jose A. Ortega Ruiz
2010-08-31 23:11 ` Jose A. Ortega Ruiz
2010-09-01 12:02 ` Ludovic Courtès
2010-09-01 20:58 ` Jose A. Ortega Ruiz [this message]
2010-09-01 22:23 ` Ludovic Courtès
2010-09-01 23:30 ` Jose A. Ortega Ruiz
2010-09-03 4:35 ` Andy Wingo
2010-09-04 1:13 ` Jose A. Ortega Ruiz
2010-09-04 17:34 ` Andy Wingo
2010-09-01 0:16 ` Jose A. Ortega Ruiz
2010-09-02 18:45 ` Jose A. Ortega Ruiz
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=87y6blyyec.fsf@newton.homeunix.net \
--to=jao@gnu.org \
--cc=guile-devel@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).