l...@gnu.org (Ludovic Courtès) writes:
>>> Do we need to talk more about what needs to be accomplished? Do we
>>> need a complete specification? Do we need a vote on if it is a good
>>> idea?
>>
>> I think you're going in the right direction. More importantly, although
>> I can't speak for them, N
Hello,
Andy Wingo writes:
> Just a random thought: we'll have to deal with unicode ports, and the
> byte-order-mark, and read-char consuming more than a byte. But perhaps
> that work can come after Guile actually supports UTF-32 internally. R6RS
> is probably a good guide in this regard, cleanly
I recently had a struggle getting slib to work with the latest guile
release (1.8.6). I believe para. 6.1.1 of the guile reference manual
needs to be rewritten since the procedures don't seem to work as
advertised. Following is the wording I suggest based on my experience
with guile 1.8.6 and the
Hello all,
Guile-Lib has moved to http://www.nongnu.org/guile-lib/, and has
switched to git. We hope that this change will make it easier for Guile
contributors to get involved with Guile-Lib, and vice versa.
Check out guile-lib from git like this:
git clone git://git.sv.gnu.org/guile-lib.git
Hi,
Just a random thought: we'll have to deal with unicode ports, and the
byte-order-mark, and read-char consuming more than a byte. But perhaps
that work can come after Guile actually supports UTF-32 internally. R6RS
is probably a good guide in this regard, cleanly distinguishing bytes
from chara
