unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: "Jose A. Ortega Ruiz" <jao@gnu.org>
Cc: guile-devel@gnu.org
Subject: Re: [PATCH] Fix for `submodules' in (ice-9 session) (closes #30062)
Date: Sat, 04 Sep 2010 10:34:41 -0700	[thread overview]
Message-ID: <m31v99mmz2.fsf@unquote.localdomain> (raw)
In-Reply-To: <8762ymwbtl.fsf@newton.homeunix.net> (Jose A. Ortega Ruiz's message of "Sat, 04 Sep 2010 03:13:10 +0200")

Hi,

On Fri 03 Sep 2010 18:13, "Jose A. Ortega Ruiz" <jao@gnu.org> writes:

> On Fri, Sep 03 2010, Andy Wingo wrote:
>
>> We can add flags to modules to indicate that they are temporary; not
>> "user modules".
>
> That'd be great. Then, we could add a (keyword) parameter to the folding
> functions to exclude (or, i think i would prefer, include) temporary
> modules in the traversal (or create new functions doing that).

You can already filter out modules whose "kind" is #f:

  scheme@(guile-user)> (module-kind (resolve-module '(ice-9 q)))
  $3 = directory
  scheme@(guile-user)> (module-kind (make-fresh-user-module))
  $4 = #f

I don't think we need an extra flag. However module "kinds" need some
retroactive design, I think...

Andy
-- 
http://wingolog.org/



  reply	other threads:[~2010-09-04 17:34 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
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 [this message]
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=m31v99mmz2.fsf@unquote.localdomain \
    --to=wingo@pobox.com \
    --cc=guile-devel@gnu.org \
    --cc=jao@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).