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
The json-abnf module creates some strange results for booleans:
(use json-abnf)
(pp (parser {\str\:\a\,\true\:true,\false\:false}))
prints:
(object (str a) (true (#t)) (false))
true is a list and false is '().
___
Chicken-users mailing list
2011/11/27 Vok Vojwo cev...@gmail.com:
The json-abnf module creates some strange results for booleans:
(use json-abnf)
(pp (parser {\str\:\a\,\true\:true,\false\:false}))
prints:
(object (str a) (true (#t)) (false))
true is a list and false is '().
I think the attached patch fixes the
