I wrote:
Here's my first batch of numerics bugfixes and other changes for
improved mathematical correctness and R6RS compliance. As far as
I can tell, they're ready to commit. Reviews solicited.
Apologies for the wasted bandwidth, but I now realize that R6RS does not
actually require that
Cool. Have you considered what you would want to do with
the 'recv!' procedure?
Hmm no. Ideas?
Perhaps the second argument could be changed to be a string, in which
case it would issue a deprecation warning, or a bytevector. But when
it’s a string, it’s bound to break unless the
Hello!
I pushed a micro-benchmark, which I used to compare the new
implementation of ‘read-line’ (commit
e578faea202a4e6eeb32e81e489b59119a2e02a0) to the previous one (before
a2c36371ce3de246bdb892afd50915ecf450df47):
* before:
(ports.bm: rdelim: read-line 1000 user 5.2)
* after:
Hey all,
Things appear to be coming together for a 2.0 release. Thanks to all
that have journeyed with us on 1.9 road; it's been fun.
The current plan is to make a 1.9.15 release next Wednesday, February 2nd,
and then to do a 2.0 release two weeks afterwards. We'll be basically
just working on
Hi,
l...@gnu.org (Ludovic Courtès) writes:
Noah Lavine noah.b.lav...@gmail.com writes:
The attached patch should add support for ECMAScript unicode literals.
I applied this one, along with corresponding test cases.
Can you please resubmit the remaining patches with test case(s) for
each,
Hi,
I finally applied them and wrote the test cases by myself.
Thanks a lot!
Thanks again for the patches, but please do write test cases next time.
I will do that. Sorry for the delay - I've been quite busy lately, and
basically all of my Guile mail has been sitting in my inbox waiting to
Hi,
I'm the guy that originally wrote this for GSOC, so I figured I'd jump
in. I'd be happy to help with getting the PEG module merge-ready.
On Wed, Jan 26, 2011 at 7:40 PM, Noah Lavine noah.b.lav...@gmail.com wrote:
Hello again,
I've attached my coverage results. The html file expects the
Hello,
I'm the guy that originally wrote this for GSOC, so I figured I'd jump
in. I'd be happy to help with getting the PEG module merge-ready.
Great!
keyword-flatten is described in api-peg.texi. It's basically a
special case of context-flatten which collapses S-expressions
according to
On Wed, Jan 26, 2011 at 8:38 PM, Noah Lavine noah.b.lav...@gmail.com wrote:
Hello,
I'm the guy that originally wrote this for GSOC, so I figured I'd jump
in. I'd be happy to help with getting the PEG module merge-ready.
Great!
keyword-flatten is described in api-peg.texi. It's basically
Hi,
It flattens until you have a list where each element either:
1. Is an atom.
or 2. Is a list whose first element is in the list of keywords.
So the car of the argument will change if it's a list that doesn't
start with the right keyword. E.g.:
(keyword-flatten '(a) '((c (a b)) (a b) (b
10 matches
Mail list logo