Re: [Json] Proposed minimal change for duplicate names in objects

[Jorge <[e-mail]>]

On 05/07/2013, at 00:17, Tatu Saloranta wrote:
> 
> At the same time, given such separation of processing layers, nothing prevents applications from doing custom serialization/deserialization, and by-passing strict checks. I don't personally mind that -- as long as ramifications are made clear, it's their responsibility -- but I don't think is universally agreed view.

I've been using JSON in a server in a language that doesn't have objects... so for the outgoing JSON texts I've had to write a custom generator for every kind of payload, manually grabbing the data from a predefined set of vars, and idem for the incoming JSON texts: .parse()ing had to fill a different predefined set of vars for each kind of payload.

This is one of those scenarios in which JSON text parsers and generators have to be ad hoc.
-- 
( Jorge )();