From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: Future of ice-9/slib.scm.
Date: Sun, 11 Dec 2005 11:59:18 +1100 [thread overview]
Message-ID: <87irtwsb2x.fsf@zip.com.au> (raw)
In-Reply-To: 87vexyatnw.fsf@trouble.defaultvalue.org
Rob Browning <rlb@defaultvalue.org> writes:
>
> With this arrangement, users who find they really need the old slib
> behavior in 1.6, will be able to set *guile-use-old-ice-9-slib* to #t.
I'd be inclined to make one radical change, and not worry about the
old stuff. Someone can still grab slib.scm from 1.6.4 or whatever if
they really need it, ie. don't want to update immediately.
> ;; These can be removed if/when we require a "new enough"
> ;; version of SLIB.
I'd also be inclined to do that now too, I don't think there's any
special merit in an old slib. Anyone wanting one can always
(presumably) run it up with "guile -lguile.init" the way slib
specifies.
> (provide 'hash)
> ...
> (if (not (defined? 'browse-url))
Without sounding like a broken record :) ... I wouldn't worry these
either. If slib has a problem then leave the fixes for there :-).
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2005-12-11 0:59 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
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 [this message]
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=87irtwsb2x.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).