Re: [Jsoncpp-devel] Backwards incompatible change in jsoncpp 64-bit support

[Aaron J. <ja...@go...>]

Hmm, but does it make sense to say a default constructed value is all
of null, an array, and an object? Wouldn't it make more sense to have
isArray (and only isArray) start returning true once the value is
"turned into" an array by appending something to it?

I'd appreciate if you could investigate the VC++ issues; I don't have
easy access to a Windows machine.