Re: [Qemu-devel] Re: [PATCH] win32: use PRId64 instead of %lld

[Avi Kivity]

On 01/26/2010 02:47 PM, Anthony Liguori wrote:
> On 01/26/2010 05:43 AM, Luiz Capitulino wrote:
> > > The issue I see isn't related to unsigned.  Apparently we currently
> > > accept values such as 'a' as valid strings. Since this is not valid 
> > > json
> > > we probably should reject it just in case we will want to switch to
> > > another json library, otherwise clients might come to depend on
> > > non-standard behaviour.
> >   This extension is only used internally by QEMU and we find it
> > very convenient otherwise we would have to escape strings in
> > dicts and lists, which is error prone and time consuming.
>
> Actually, I was reading the JSON RFC last night and came across:
>
>   "A JSON parser transforms a JSON text into another representation. A
>    JSON parser MUST accept all texts that conform to the JSON grammar.
>    A JSON parser MAY accept non-JSON forms or extensions."
>
> So we are fully JSON compliant in our current implementation.

The risk is that if we support a private extension (like '') and then 
json is officially extended to support a conflicting or similar syntax 
with a different meaning, then we cannot advance to the next revision of 
json without breaking compatibility.

In the case of '', the odds of a such a clash are very low, but 
nevertheless I think we should refrain from doing so.  Being strict is good.

--
error compiling committee.c: too many arguments to function