Rob Browning writes:
>
> The question then is, how should we fix this, both in 1.6 and in
> future releases? (I've spoken to the SLIB author, and he's interested
> in working with us.)
how about converting the individual slib files into guile modules?
Klaus Schilling
Hi Klaus,
On Wed, 2005-11-16 at 08:50 +0100, klaus schilling wrote:
> how about converting the individual slib files into guile modules?
I thought about this in the past. It is however a maintainance
nightmare. If you don't believe me you are free to try it and see ;)
Cheers,
--
Andy Wingo
http
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.
[EMAIL PROTECTED] (Ludovic Courtès) writes:
> Agreed, this approach is consistent with the current `load' stack.
>
> The patch below does what you described. I left the `#:reader' option
> to `define-module' as an alternative, higher-level approach to choosing
> an alternate reader.
>
> Please le
[EMAIL PROTECTED] (Ludovic Courtès) writes:
> Hello,
>
> Neil Jerram <[EMAIL PROTECTED]> writes:
>
>> Nice work, but it looks to me that PUSH_REF sets the value of the
>> (pstate->top)th element _before_ incrementing pstate->top. So
>> shouldn't your fix do the decrement first and then set the sl
