Rob Browning <[EMAIL PROTECTED]> writes:
> 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?
With respect to some of the *features*, it looks like guile.init
handles 'random by just adding the two functions that Guile's native
implementation was missing. I think this probably means that the
FIXME in slib.scm has been fixed, and Guile doesn't need to
inappropriately remove 'random from *features* anymore.
Similarly, it looks like the slib.scm ENHANCE-ME regarding arrays may
be satisfied by the current guile.init. It appears that guile.init
arranges for Guile's native arrays to function correctly as SLIB
arrays. If so, then it should be OK to drop the slib.scm code that
removes 'array from *features*, but someone else may want to
double-check.
I've examined much of the rest of the slib.scm code and sent a few
questions upstream. At this point, I think I have a pretty good idea
about what should be done with almost all of the code except the
following:
- slib:eval -- should it be using slib-module or
interaction-environment?
- slib:load -- see the FIXME there.
- *vicinity-table*, install-require-vicinity, and
install-require-module -- these don't exist in guile.init (or
SLIB). Do we still want or need them?
Thanks
--
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
