Hi!
Thanks for the update!
Thien-Thi Nguyen skribis:
>> i'd like to apply the fix myself (in the savannah repo), onto
>> ‘branch_release-1-8’.
>
>Yes, please do! Can you apply it to stable-2.0 as well?
>
> Sorry, no; i lack sufficient bandwidth.
OK, I’ll do it if nobody beats me a
() l...@gnu.org (Ludovic Courtès)
() Sat, 25 Aug 2012 16:24:26 +0200
> Looking to move WIKID[0] out of the Guile 1.4.x ghetto (which is
> pretty cozy, i must say),
(Speaking of which, do let me know when rpx has left the ghetto,
too. :-))
OK, will do. If the world doesn't end, a cou
Hi,
Mike Gran skribis:
> The big issues with moving to 2.0 that I've seen expressed are
> non-portability,
I don’t think 2.0 is less portable than 1.8; there’s room for
improvement (MinGW, pthread support), but it’s not a disaster either.
> number of dependencies,
There’s are two on-going thi
> From: Ludovic Courtès
>> I imagine if this particular fix goes smoothly, i will be motivated to
>> continue w/ this kind of maintenance work, where the focus is on
>> continuity and stability (perhaps likewise showing 1.6 and 1.4 some
>> love, as well).
>
> Hmm, I’d find it more important
Hi Thien-Thi!
Thien-Thi Nguyen skribis:
> Looking to move WIKID[0] out of the Guile 1.4.x ghetto (which is pretty
> cozy, i must say),
(Speaking of which, do let me know when rpx has left the ghetto, too. :-))
> i ran into a Guile 1.8 problem. Apparently, ‘send’ gratuitously
> demands its MES
Looking to move WIKID[0] out of the Guile 1.4.x ghetto (which is pretty
cozy, i must say), i ran into a Guile 1.8 problem. Apparently, ‘send’
gratuitously demands its MESSAGE arg (a string) be writable. This loses
if, e.g., MESSAGE is the result of ‘symbol->string’. Here is the fix:
libguile/s
