Hello,
Thank you for your bug report, and for your efforts to harmonize the
different JSON implementations. I have made the changes you suggest,
except for the following:
- due to a limitation in abnf/lexgen-derived parsers, #f cannot be a
value returned by a parser. So the JSON true and
2011/11/28 Ivan Raikov ivan.g.rai...@gmail.com:
- due to a limitation in abnf/lexgen-derived parsers, #f cannot be a
value returned by a parser. So the JSON true and false values are
represented by '(#t) and '(#f).
Can you explain this? I tried my patch with some booleans and it seems to
On Sun, Nov 27, 2011 at 06:39:52PM +0100, Moritz Heidkamp wrote:
Vok Vojwo cev...@gmail.com writes:
I think the Medea egg intends to do it the right way. But it seems to be
buggy.
And it has a voracious appetite
It does indeed :-)
Medea fails to parse the data:
(use medea)
I'm writing an implementation of SRFI-1 in Javascript (just for fun) and I
have a question about SRFI-1's any procedure. In the docs it says that
(any) does not return a simple boolean (#t or #f), but a general value,
however it also says that any must be called with a procedure taking n
On Nov 28, 2011, at 9:01 PM, Nick Zarr wrote:
I've been testing my implementation against Chicken for correctness and
here's what I get on Chicken:
#;2 (any (lambda (x) (if (even? x) x)) '(1 2 3))
#;3 (any (lambda (x) (even? x)) '(1 2 3))
#t
#;4 (any even? '(1 3 5))
#f
For #3 and #4
Nick Zarr scripsit:
I'm writing an implementation of SRFI-1 in Javascript (just for fun) and I
have a question about SRFI-1's any procedure. In the docs it says that
(any) does not return a simple boolean (#t or #f), but a general value,
however it also says that any must be called with a
