Re: [Json] serializing sequences of JSON values

Those I've used keep track of state only insofar as what is required to write out an object or array. At least those I've used do not keep track of state between serialization calls.

In any case, I won't keep belaboring the issue. It's done.

Paul

-------- Original Message --------
From: Tatu Saloranta <tsaloranta@gmail.com>
Sent: March 9, 2014 6:33:29 PM CET
To: John Cowan <cowan@mercury.ccil.org>
Cc: Larry Masinter <masinter@adobe.com>, Pete Resnick <presnick@qti.qualcomm.com>, Bjoern Hoehrmann <derhoermi@gmx.net>, Paul Hoffman <paul.hoffman@vpnc.org>, "json@ietf.org" <json@ietf.org>, "Paul E. Jones" <paulej@packetizer.com>, Tim Bray <tbray@textuality.com>, "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>, "Matt Miller (mamille2)" <mamille2@cisco.com>, Barry Leiba <barryleiba@computer.org>, "rfc7158@schmorp.de" <rfc7158@schmorp.de>
Subject: Re: [Json] serializing sequences of JSON values

The way real-life serializers do this is to keep track of state. If a root
value has been output, then insert a separator. If not, then not. Expecting
caller to pass this state would indeed be silly.

I still find it fascinating how much of discussion is based on theoretical
aspect of ifs, whys and maybes. But not in observing how things have been
done for years now.

-+ Tatu +-

On Sun, Mar 9, 2014 at 2:36 PM, John Cowan <cowan@mercury.ccil.org> wrote:

> Larry Masinter scripsit:
>
> > If you want to write out a sequence of JSON values you would write them
> out as an array with [] around and comma separators.
>
> That would be a single JSON value, not a sequence thereof.
>
> --
> Income tax, if I may be pardoned for saying so,         John Cowan
> is a tax on income.  --Lord Macnaghten (1901)           cowan@ccil.org
>
> _______________________________________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/listinfo/json
>