From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: Future of ice-9/slib.scm.
Date: Sat, 19 Nov 2005 17:06:54 -0800 [thread overview]
Message-ID: <87acg03z69.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <87y83kyzs4.fsf@zagadka.de> (Marius Vollmer's message of "Sun, 20 Nov 2005 01:38:03 +0200")
Marius Vollmer <mvo@zagadka.de> writes:
> Whenever we want to do things differently, we should push those
> changes into SLIB.
Certainly. That's what I assume we're trying to determine here.
i.e. are there any changes in the current slib.scm that haven't made
it upstream, but should?
For example, aside from the "eval in interaction-environment vs slib"
issue, see also the comments in slib.scm regarding *features* and
slib:load. Do we need or want to preserve any of those changes?
--
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2005-11-20 1:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 5:23 Future of ice-9/slib.scm Rob Browning
2005-11-16 7:50 ` klaus schilling
2005-11-16 10:14 ` Andy Wingo
2005-11-17 19:16 ` Rob Browning
2005-11-16 15:38 ` Greg Troxel
2005-11-18 3:56 ` Rob Browning
2005-11-18 11:46 ` Greg Troxel
2005-11-19 14:22 ` Marius Vollmer
2005-11-19 18:09 ` Rob Browning
2005-11-19 21:43 ` Rob Browning
2005-11-19 23:38 ` Marius Vollmer
2005-11-20 1:06 ` Rob Browning [this message]
2005-11-20 20:01 ` Rob Browning
2005-11-20 21:09 ` Kevin Ryde
2005-11-20 23:27 ` Rob Browning
2005-12-09 20:42 ` Rob Browning
2005-12-11 0:59 ` Kevin Ryde
2005-12-11 6:08 ` Rob Browning
2005-12-12 19:39 ` Greg Troxel
2005-12-13 1:33 ` 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=87acg03z69.fsf@trouble.defaultvalue.org \
--to=rlb@defaultvalue.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).