Hi Mike,
Mike Gran writes:
> First, let me note the ways that r6rs ports and Guile legacy ports are
> different:
>
> 1. Encoding is a property of the port vs a property of a transcoder
>
> R6RS have transcoder objects that describe a conversion as well
> as the state of the conversion.
Le Thu, 08 Apr 2010 20:53:17 +0200,
Andy Wingo a écrit :
> Hi David,
>
> I'm happy to help, and glad to hear things are going OK. You probably
> have the largest guile-gnome-using apps out there... Also, one of these
> three lists is probably enough ;)
:-) left guile-devel only this time
> On
forgot to attach postgres.scm ...
Le Thu, 08 Apr 2010 20:53:17 +0200,
Andy Wingo a écrit :
> Hi David,
>
> I'm happy to help, and glad to hear things are going OK. You probably
> have the largest guile-gnome-using apps out there... Also, one of these
> three lists is probably enough ;)
:-) le
Hi-
> From: Ludovic Courtès l...@gnu.org
> Section 8.2.4 of r6rs-lib says that transcoders are “possibly stateful”,
> but it also says that they are immutable. So I guess a possible
> implementation is to have transcoders stateless and immutable, e.g.,
> (define (latin-1-codec)
> "ISO-8859-
Hi Mike,
Mike Gran writes:
> It would be easier. When thinking about this, I was remembering or
> mis-remembering that, back in the 2009, you'd said some along the
> lines of ultimately standardizing on the R6RS ports codebase, and that
> I was to consider the work on Guile legacy ports as inte
Hi
> From: Ludovic Courtès l...@gnu.org
>> It would be easier. When thinking about this, I was remembering or
>> mis-remembering that, back in the 2009, you'd said some along the
>> lines of ultimately standardizing on the R6RS ports codebase, and that
>> I was to consider the work on Guile le
Hi-
I wonder if I might be able to convince one of you fine
gentlemen to hack together a version of scm_c_define_gsubr
that takes a locale C string as a docstring.
I would find it most useful.
Thanks,
Mike
Hi,
Mike Gran writes:
>> From: Ludovic Courtès l...@gnu.org
>
>>> It would be easier. When thinking about this, I was remembering or
>>> mis-remembering that, back in the 2009, you'd said some along the
>>> lines of ultimately standardizing on the R6RS ports codebase, and that
>>> I was to cons
Hi Mike and Ludo,
>> Works for me. Some questions that will have to be answered.
>> Is there a C API for raising R6RS error conditions?
>
> No, not yet. Actually, Julian’s work on R6RS libraries isn’t merged
> yet.
FWIW, the way this works right now on the wip-r6rs-libraries branch is
that R6R
Hi Ludo,
I've got some status updates:
> As I said, there aren't that many libraries left to do. Off the top
> of my head, the still-missing ones are (rnrs eval), (rnrs arithmetic
> fixnums), (rnrs arithmetic flonums), and the composite library, (rnrs
> rnrs). I also want to move the library f
10 matches
Mail list logo