rdmenezes/jzon

Automatically exported from code.google.com/p/jzon

jzon's Issues

rootNode.Get() crashes on not existing key

Calling 

rootNode.Get("ThisIsAKeyName").AsString();

crashes, if the key "ThisIsAKeyName" does not exist. Is there a chance to 
detect if a key exists or not?

Original issue reported on code.google.com by [email protected] on 4 Oct 2012 at 1:10

Add error handling

Add a way to handle errors from the parser when trying to parse an invalid file.

Original issue reported on code.google.com by [email protected] on 8 Sep 2011 at 7:01

An empty array is parsed as an array with a null value

The following file
{
  "array": []
}
will be parsed as
{
  "array": [ null ]
}

Original issue reported on code.google.com by [email protected] on 9 Mar 2011 at 5:35

No proper documentation

* Expand the wiki
* Generate doxygen documentation

Original issue reported on code.google.com by [email protected] on 22 May 2011 at 3:31

Getting error in ToString method

Getting  below error 
"Unhandled exception at 0x751c969b in JParser.exe: Microsoft C++ exception: 
Jzon::TypeException at memory location 0x001ef4a4.." 
in ToString method with below json string


{
    "jsondata": [
        {
            "selector": "#username",
            "action": "fill",
            "type": "text",
            "value": "testuser"
        },
        {
            "selector": "#password",
            "action": "fill",
            "type": "password",
            "value": "admin@123"
        },
        {
            "selector": "sign",
            "action": "mouseover",
            "type": "button"
        }
    ]
}

Original issue reported on code.google.com by [email protected] on 23 Oct 2013 at 6:35

[deleted issue]

[deleted issue]

Escape certain characters

Some characters should be escaped before being written, for example the " 
character.

Original issue reported on code.google.com by [email protected] on 8 Sep 2011 at 7:39

MSVC 2008 compilation error

Please check Jzon compilation on MS Visual C++ 2008.

Original issue reported on code.google.com by NtVisigoth on 2 Mar 2012 at 9:11

interpretValue function is number check doesn't work for number in scinotation format like "1.32E4"

If the number is in sci-notation format, the following code in 
Parser::interpretValue function would fail.

for (std::string::const_iterator it = value.begin(); it != value.end(); ++it)
{
   if (!isNumber(*it))
  {
    number = false;
    break;
  }
}

It should be changed to the following code:
bool number = true;
try
{
    double d = std::stod(value);
}
catch (const std::exception& e)
{
    number = false;
}

Original issue reported on code.google.com by [email protected] on 3 Apr 2014 at 5:46

Negative values are not handled

Negative values (int or double) are not handled and are parsed as NULL.

Original issue reported on code.google.com by [email protected] on 13 May 2011 at 3:47

Warnings, GetCount()

MicroSoft Visual C++ 2010:

    unsigned int Object::GetCount() const
    {
        return children.size();
    }
...
    unsigned int Array::GetCount() const
    {
        return children.size();
    }

Two warnings:
1>..\third_party\Jzon\Jzon.cpp(650): warning C4267: 'return' : conversion from 
'size_t' to 'unsigned int', possible loss of data
1>..\third_party\Jzon\Jzon.cpp(840): warning C4267: 'return' : conversion from 
'size_t' to 'unsigned int', possible loss of data


On Win-64 platform:

sizeof(unsigned int) : 4
sizeof(size_t) : 8

Original issue reported on code.google.com by NtVisigoth on 2 Mar 2012 at 10:11