11-23-2012, 12:05 AM
(11-22-2012, 08:24 PM)xoft Wrote: Rev 1057 should have the assertion all fixed, does it work for you or do you still get them?The assertions still appear in the r1060 debug build, the release build is ok.
(11-22-2012, 08:24 PM)xoft Wrote: Also, could you possible sum up the differences in the library upgrades? Just to list the reasons why we should upgrade, rather than staying with the version that's working okay for us. :)Mostly upstream bugfixes, the major revision/version changes:
Jsoncpp (r139 -> r250)
- Bug #2934500: Removed experimental ValueAllocator, it caused static initialization/destruction order issues.
- Bug #3139677: JSON [1 2 3] was incorrectly parsed as [1, 3]. Error is now correctly detected.
- Fixed a hard to debug crash on OS X related to sscanf format strings.
- Made two security fixes.
- Fixed a parsing bug in decodeNumber
- Another round of attempting to fix VC++ errors...
- Bug#3306345: minor typo in Path::resolve()
- Bug#2407932: strpbrk() could fail for NULL pointer.
- Bug #6: Disable some inline assembler code from crypto++ causing compiler segfault
- Fixed some gcc 4.6 compile errors
- Bug#76: fix for Valgrind error
- Wrong code generation for some particular boolean expressions.
- luaV_settable may invalidate a reference to a table and try to reuse it.
- GarbageCollector may get stuck during parsing and avoids proper resizing of the string table, making its lists grow too much and degrading performance.
- io.read("*n","*n") may return garbage if second read fails.
- Newindex metamethod may not work if metatable is its own metatable.
- Parser may collect a prototype while building it.