unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: Andy Wingo <wingo@pobox.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>, guile-devel@gnu.org
Subject: Re: Why Ice-9?
Date: Wed, 14 Jul 2010 08:28:29 +0200	[thread overview]
Message-ID: <87k4oyr302.fsf@ambire.localdomain> (raw)
In-Reply-To: <m3eif7axjw.fsf@unquote.localdomain> (Andy Wingo's message of "Tue, 13 Jul 2010 23:20:35 +0200")

() Andy Wingo <wingo@pobox.com>
() Tue, 13 Jul 2010 23:20:35 +0200

   There are also submodule binders, in git guile, that can be used to
   implement this.

Cool, i'll take a look at submodule binders.

   > - Module name directory part (of aliases, of fully-resolved) 
   >   must be non-empty?
   >
   > - Will dealing with ‘%load-extensions’ be in the future plans?
   >
   > - Where/how to store alias info.  Can this mechanism be unified
   >   with one for resolved modules (e.g., Guile 1.4.x module catalogs)?

   I don't understand the problem solved by these things; I would need more
   details to comment, I think.

The first and third are issues analogous to design of symbolic links on a
filesystem.  The ‘%load-extensions’ question is orthogonal.

thi



      reply	other threads:[~2010-07-14  6:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-09 17:59 Why Ice-9? Noah Lavine
2010-07-09 19:07 ` Andy Wingo
2010-07-09 19:44   ` Andreas Rottmann
2010-07-10 14:17   ` Ludovic Courtès
2010-07-12  8:07     ` Thien-Thi Nguyen
2010-07-13 21:20       ` Andy Wingo
2010-07-14  6:28         ` Thien-Thi Nguyen [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://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=87k4oyr302.fsf@ambire.localdomain \
    --to=ttn@gnuvola.org \
    --cc=guile-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=wingo@pobox.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.
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).