Filed all issues.
On Wed, Jan 2, 2019 at 6:44 PM Aleix Conchillo Flaqué
wrote:
> Hi,
>
> On Wed, Jan 2, 2019 at 7:14 AM John Cowan wrote:
> >
> > I'm not sure where best to report these, so sending this email.
> >
>
> Same as before, github issues should work.
>
> > JSON numbers have to be, in
Hi,
On Wed, Jan 2, 2019 at 7:14 AM John Cowan wrote:
>
> I'm not sure where best to report these, so sending this email.
>
Same as before, github issues should work.
> JSON numbers have to be, in Scheme terms, either exact integers or inexact
> reals excluding +inf.0, -inf.0, and +nan.0. Guil
On Wed, Jan 2, 2019 at 6:31 AM John Cowan wrote:
>
> In the current version of guile-json, JSON null is represented internally as
> #nil. Because of the magic behavior of #nil, this causes certain problems
> when trying to discriminate between various internal JSON representations.
> For exam
I'm not sure where best to report these, so sending this email.
JSON numbers have to be, in Scheme terms, either exact integers or inexact
reals excluding +inf.0, -inf.0, and +nan.0. Guile-json will blithely
output any of these three as well as 1/2, 3.4+5.6i, etc., which will not
work with other
In the current version of guile-json, JSON null is represented internally
as #nil. Because of the magic behavior of #nil, this causes certain
problems when trying to discriminate between various internal JSON
representations. For example, the programmer will expect (list? j) to
detect a JSON obje
