lua-cjson, branch 2.1.0.19

bugfix: fix C99 for-loop declaration for GCC 4.8.5 C89 compatibility

2026-06-28T11:38:40+00:00

bugfix: setting encode_escape_forward_slash on a cjson instance does not affect other instances.

2026-06-14T13:30:49+00:00

bugfix: own a copy of the encode_indent string

2026-06-07T12:39:00+00:00

json_cfg_encode_indent stored the raw luaL_checkstring pointer, which aliases a Lua string that can be garbage-collected, causing a use-after-free / heap info-leak on a later encode(). Store a malloc'd copy, freed on reset and in __gc.

bumped versoin to 2.1.0.17.

2026-05-06T13:23:33+00:00

optimize: rename cjson.decoce_allow_comments to cjson.decocde_allow_comment.

2026-02-10T01:08:52+00:00

reslove two warnings and update the doc.

feature: add option to allow comments in decode.

2026-02-10T00:59:11+00:00

feature: add option to indent encoded output.

2026-01-19T00:51:57+00:00

Fixed: worning for explicit pointer to int conversion.

2026-01-19T00:44:59+00:00

bumped to to v2.1.0.16

2026-01-19T00:17:26+00:00

bugfix: fix truncation of decoded numbers outside lua_Integer's range (#116)

2025-10-30T02:35:41+00:00

json_next_number_token stores the `long long` return value from `stroll` in a `lua_Integer` (which is typically a typedef for `ptrdiff_t`). On 32-bit platforms, this ends up storing an 8-byte number into a 4-byte variable, truncating the value. Instead, store the converted value in a temporary `long long` variable so we can detect the scenario and decode into a `lua_Number`. Signed-off-by: James McCoy