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

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

Alright, I've implemented my understanding of the desired behavior in SVN
revision 216, documenting the change in NEWS.txt.

A few questions:

 *  Could you take a look at NEWS.txt and tell me whether you agree with the
    behavior? I made changes to the other isFoo methods to make them more
    consistent and less surprising (for example, I don't know why null
    returned true for isArray).

 *  It feels like now that these completely describe the safety of the asFoo
    methods, the isConvertibleTo method is redundant. It's also not completely
    descriptive, since it doesn't distinguish 64-bit integers. Should I delete
    it? We don't ever use it at Google, but I suppose this may be a problem
    for other codebases.

Aaron