From: Greg Troxel <gdt@ir.bbn.com>
Cc: guile-devel@gnu.org
Subject: Re: Future of ice-9/slib.scm.
Date: 16 Nov 2005 10:38:32 -0500 [thread overview]
Message-ID: <rmiek5gfvrb.fsf@fnord.ir.bbn.com> (raw)
In-Reply-To: <878xvpupx0.fsf@trouble.defaultvalue.org>
How important is it that 1.6's behavior with respect to older versions
of SLIB (versions that already worked) remain unchanged? Certainly
someone already using guile 1.6.7 successfully with some older version
of SLIB might not be happy if 1.6.8 no longer worked with their SLIB
install.
A good question. While I'm generally in favor of backwards
compatibility, I suspect that people tend to upgrade slib without a
lot of issues (other than this one).
One very strict way to approach this would be to do something like
this in ice-9/slib.scm:
(if (detect-older-slib?)
(load-from-path "old-slib.scm")
(load-from-slib "guile.init"))
An easier approach is to put in the if, but with *use-old-slib-init*,
define that to #f, and put in NEWS to set that to #t if trouble. That
gives people a low-grief way to recover, but without a lot of
guile maintainer time.
I would expect that as long as the older slib version has the
define->define-public hack then the guile.init that came with it would
work fine.
--
Greg Troxel <gdt@ir.bbn.com>
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2005-11-16 15:38 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 [this message]
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
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=rmiek5gfvrb.fsf@fnord.ir.bbn.com \
--to=gdt@ir.bbn.com \
--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).