From: Andreas Rottmann <a.rottmann@gmx.at>
To: Andy Wingo <wingo@pobox.com>
Cc: Noah Lavine <noah.b.lavine@gmail.com>, guile-devel@gnu.org
Subject: Re: Why Ice-9?
Date: Fri, 09 Jul 2010 21:44:44 +0200 [thread overview]
Message-ID: <87wrt45tjn.fsf@delenn.lan> (raw)
In-Reply-To: <m3630opj7c.fsf@unquote.localdomain> (Andy Wingo's message of "Fri, 09 Jul 2010 21:07:51 +0200")
Andy Wingo <wingo@pobox.com> writes:
> On Fri 09 Jul 2010 19:59, Noah Lavine <noah.b.lavine@gmail.com> writes:
>
>> I am not completely sure this is the right place to ask this, but why
>> do many of the module names in Guile start with 'ice-9'?
>>
>> I can tell you that as a newcomer this is quite unintuitive.
>
> Heh, I thought that too, once.
>
> http://en.wikipedia.org/wiki/Ice-nine
>
> The idea at the time (1998 or so) was that Guile's module system would
> crystallize the mass of Scheme code out there. It didn't happen exactly
> like that; in practice ice-9 is Guile's namespace.
>
> Now, there is a deeper issue here -- a global Scheme namespace is
> starting to emerge, and Guile is a bit all over the map. To me it's fine
> to have e.g. statprof have the toplevel module, (statprof), even though
> it's part of Guile; but in a way I feel that instead of having ice-9 and
> system, we should just have (guile) as our module prefix, in the same
> way that e.g. ikarus and chez scheme have (ikarus ...) and (chezscheme
> ...), respectively.
>
> It's too late to do that this cycle, but perhaps during 2.0 or for 2.2
> we could provide (ice-9 popen) as an alias to (guile popen), and
> eventually for 2.4 deprecate both ice-9 and system. Just a thought,
> though...
>
+1 for that idea from me.
Rotty
--
Andreas Rottmann -- <http://rotty.yi.org/>
next prev parent reply other threads:[~2010-07-09 19:44 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 [this message]
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
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=87wrt45tjn.fsf@delenn.lan \
--to=a.rottmann@gmx.at \
--cc=guile-devel@gnu.org \
--cc=noah.b.lavine@gmail.com \
--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).