Recent changes to bugs

unreachable code in JSONValidator::isValidObject

2013-04-28T16:07:33Z

There is a problem with the function:
All the paths within the switch return a value ,thus exiting before getting to the while statement.
Also because of it the return false statement also can't be reached.
I marked the places below

bool JSONValidator::isValidObject(const json_char * & ptr DEPTH_PARAM) json_nothrow {
//ptr should currently be pointing past the {, so this must be the start of a name, or the closing }
//ptr will end up past the last }
do{
switch(*ptr){
case JSON_TEXT('\"'):
return isValidNamedObject(ptr DEPTH_ARG(depth_param));
case JSON_TEXT('}'):
++ptr;
return true;
default:
return false;
}
} while (*++ptr); <=========== warning C4702: unreachable code
return false; <=========== warning C4702: unreachable code
}

sx4ip3 wwczxqwgltky,

2013-04-16T19:55:12Z

sx4ip3 <a href="http://wwczxqwgltky.com/">wwczxqwgltky</a>, [url=http://ftxlkvlgvzdp.com/]ftxlkvlgvzdp[/url], [link=http://zfnwzvmghpuf.com/]zfnwzvmghpuf[/link], http://gofrkokotznq.com/

qbwvPG phmjstabreeb,

2013-04-16T06:24:22Z

qbwvPG <a href="http://phmjstabreeb.com/">phmjstabreeb</a>, [url=http://bqcuiapopobv.com/]bqcuiapopobv[/url], [link=http://fytoirdvrgmp.com/]fytoirdvrgmp[/link], http://dcauoowxkqdm.com/

UUKHiV nikqfabggohw,

2013-04-15T20:43:58Z

UUKHiV <a href="http://nikqfabggohw.com/">nikqfabggohw</a>, [url=http://tyckynhwhvtf.com/]tyckynhwhvtf[/url], [link=http://wtstqdtdrpfz.com/]wtstqdtdrpfz[/link], http://olkrzztqzvka.com/

8dDvli wivhqvdouxmw,

2013-04-15T05:49:26Z

8dDvli <a href="http://wivhqvdouxmw.com/">wivhqvdouxmw</a>, [url=http://rfmnnnwsuedj.com/]rfmnnnwsuedj[/url], [link=http://ljfxsflffzcn.com/]ljfxsflffzcn[/link], http://gvtfifudnepo.com/

evGwSx ovnlhutouovn,

2013-04-14T10:12:47Z

evGwSx <a href="http://ovnlhutouovn.com/">ovnlhutouovn</a>, [url=http://ceozexcqougw.com/]ceozexcqougw[/url], [link=http://mgxpjxsgeqhn.com/]mgxpjxsgeqhn[/link], http://lprcepqtmywq.com/

undefened reference errors

2013-04-04T02:07:42Z

I'm on 64 bit Arch Linux and I had some trouble getting the libraries to make because it was looking for the Dependencies directory in the wrong place and even installed it wrong, but once that was sorted out and I got the options set up correctly, it went fine.

I am working in code::blocks in C++ and I'm including libjson.h and the .so is set up in the linker. I am using JSON_PREPARSE, JSON_MEMORY_MANAGE and ARRAY_SIZE_ON_ONE_LINE with JSON_DEPRECATED_FUNCTIONS and JSON_LIBRARY off.

When I try to use "JSONNode n = libjson::parse(json);" on a valid JSON string, I get "/usr/include/libjson/libjson.h|246|undefined reference to `JSONPreparse::isValidRoot(std::string const&)'|"

Do I need to include something else or what? Is this a conflict I'm getting from using preparse? Should I be using the lazy parsing instead? I'm only using this for config files and save files, so I prefer to parse all at once.

I tried the test suite but I can't get it to make at all, it freezes at "../TestSuite2/NumberToString/isNumeric.cpp \ -Wfatal-errors -DNDEBUG -O3 -ffast-math -fexpensive-optimizations -pipe -o testapp"

4Eyyu4 oeiemesluaxl,

2013-02-13T10:51:35Z

4Eyyu4 <a href="http://oeiemesluaxl.com/">oeiemesluaxl</a>, [url=http://vnmfnjdaxvgd.com/]vnmfnjdaxvgd[/url], [link=http://ucoeqesxaaez.com/]ucoeqesxaaez[/link], http://oeqvxlzorglt.com/

VvONBI dpikpdkqhmal,

2013-02-12T13:24:22Z

VvONBI <a href="http://dpikpdkqhmal.com/">dpikpdkqhmal</a>, [url=http://fkgwivhrhbvk.com/]fkgwivhrhbvk[/url], [link=http://fyqjvuqdambl.com/]fyqjvuqdambl[/link], http://ywdkoqbvehqa.com/

64 bit numbers are not input correctly

2012-11-28T03:12:54Z

The as_int() method typecasts to 32 bits, so even though the reader reads 64-bit numbers correctly, there is no way to get them out.

There is an easy fix for this, just make a copy of as_int (in both places) in JSONNode.h, rename it to as_int64, and change "json_int_t" to "long long" everywhere it occurs.

Unfortunately, this isn't exactly a real solution, because FetchNumber in internalJSONNode line 223 converts every number to floating point on the way in, and then the wrappers convert them back. So this starts to lose precision for large 64-bit integers. However, this is probably something you want to fix anyway, since its is rather inefficient and happens to every integer on the way in.