unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: Future of ice-9/slib.scm.
Date: Thu, 17 Nov 2005 19:56:10 -0800	[thread overview]
Message-ID: <87psoyhan9.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: rmiek5gfvrb.fsf@fnord.ir.bbn.com

Greg Troxel <gdt@ir.bbn.com> writes:

> 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.

Hmm.  If there isn't an easy way to detect the SLIB version, then
that'd definitely be worth considering.

> 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
> define->would
> work fine.

Indeed.  If I felt relatively certain that just calling

      (load-from-slib "guile.init")

would do the right thing with the current SLIB version, then I'd be
inclined to consider that as a solution, even in 1.6.8, whenever we
detect a "newer" SLIB[1].

However, to have a good sense that loading guile.init *would* "do the
right thing", I or someone else probably needs to go through
guile.init with reasonable care, while consulting the current
slib.scm, to make sure the differences look "OK".  My suspicion is
that much of guile.init is just fine, but there are some comments in
slib.scm that may warrant a bit of investigation.

If there's anyone else here who has the time and wants to attempt that
evaluation (and probably raise questions here), then that would be
great.  Otherwise, I'll try to get to it soon, though it might not be
until this weekend at the earliest.


[1] Though actually, the current SLIB release still has the unix/UNIX
  symbol case issue (which has been fixed in CVS).  I believe it also
  doesn't define the (ice-9 slib) module if it detects guile 1.6, so
  we'd still need at least a small wrapper.

-- 
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


  reply	other threads:[~2005-11-18  3:56 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 [this message]
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=87psoyhan9.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).