From: Kevin Ryde <user42@zip.com.au>
To: guile-devel@gnu.org
Subject: Re: SLIB
Date: Thu, 16 Aug 2007 09:05:07 +1000 [thread overview]
Message-ID: <87fy2kxuu4.fsf@zip.com.au> (raw)
In-Reply-To: <66e540fe0708111000v22662b54sc62a9b297bf6308e@mail.gmail.com> (Mikael Djurfeldt's message of "Sat, 11 Aug 2007 19:00:08 +0200")
"Mikael Djurfeldt" <mikael@djurfeldt.com> writes:
>
> slib.scm makes sure that each time
> some module requires new slib code, it will be loaded into the module
> (ice-9 slib) and exported from there. I'm not at all sure that
> guile.init does that,
I suspect it doesn't. It'd be cute if going through (ice-9 slib) worked
with the module system so you could get slib in some modules and not
others. In particular it'd help for the various funcs in slib which
clash with guile core bits, like the different flavour of `system', and
the separate `provided?' feature list which Greg mentioned. But I think
it depends what Aubrey want to do. For now I think guile.init is only
really setup to be loaded into the top-level environment to transmute it
into an slib environment.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2007-08-15 23:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-11 11:36 SLIB Ludovic Courtès
2007-08-11 17:00 ` SLIB Mikael Djurfeldt
2007-08-15 23:05 ` Kevin Ryde [this message]
2007-08-16 8:24 ` SLIB Mikael Djurfeldt
2007-08-16 22:43 ` SLIB Kevin Ryde
2007-09-03 0:42 ` SLIB Rob Browning
2007-09-03 7:22 ` SLIB Ludovic Courtès
2007-09-04 5:23 ` SLIB Rob Browning
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=87fy2kxuu4.fsf@zip.com.au \
--to=user42@zip.com.au \
--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).