json-c: issues_closed_for_0.17

json-c 0.18

issues_closed_for_0.17

This list was created with:

    PREV=2022-04-13
    NOW=2023-08-12
    curl "https://api.github.com/search/issues?q=repo%3Ajson-c%2Fjson-c+closed%3A>${PREV}+created%3A<${NOW}&sort=created&order=asc&per_page=100&page=1" > issues1.out
    jq -r '.items[] | "[" + .title + "](" + .url + ")" | tostring' issues?.out > issues.md
    sed -e's,^\[ *\‍(.*\‍)\](https://api.github.com/.*/\‍([0-9].*\‍)),* [Issue #\2](https://github.com/json-c/json-c/issues/\2) - \1,' -i issues.md
    cat issues.md >> issues_closed_for_0.17.md

- Issue #191 - Override int64 to only display uint64 strings
- Issue #537 - Replace '\0' only when parsing key, not change data in value.
- Issue #570 - Figure out what needs to be done with Android.configure.mk
- Issue #587 - Store the hashValue to avoid repeating the hash calculation during the hash resize.
- Issue #612 - json-c-0.11: Fix CVE-2020-12762 - json-c through 0.14 has an integer overflow and out-of-bounds write ...
- Issue #620 - Introduce json_object_new_string_{ext,noalloc}().
- Issue #624 - json-c-0.14: Detect broken RDRAND during initialization.
- Issue #625 - json-c-0.13.x: Detect broken RDRAND during initialization.
- Issue #668 - Memory usage regression due to newlocal() on older FreeBSD releases
- Issue #676 - dereferencing type-punned pointer might break strict-aliasing rules [-Werror=strict-aliasing]
- Issue #677 - Naming conflict when using both json-c and jansson
- Issue #679 - Let json-c be used with obsolete compilers
- Issue #681 - json_tokener_parse_ex: `null` (4 bytes) only parses as valid JSON when passed with null terminator (5 bytes). Documentation issue?
- Issue #686 - Remove dependency on libM::getrandom
- Issue #687 - Does not build on Apple Silicon M1
- Issue #688 - json-c-0.15-nodoc.tar.gz build fails
- Issue #702 - json_patch: add first implementation only with patch application
- Issue #704 - add json_object_array_insert_idx() + test-cases + fix json_pointer doc-strings
- Issue #705 - segmentation fault on json-c parsing methods in cross compiled target
- Issue #721 - cmake test fails with building json-c with icc
- Issue #730 - Need a comparison with other JSON libraries in C
- Issue #733 - Official release? 1.0?
- Issue #756 - Question: Is there any way to build this with Gnu Make?
- Issue #757 - json_object_from_fd_ex: fail if file is too large
- Issue #759 - json_tokener_parse_ex: handle out of memory errors
- Issue #766 - Some people have trouble with undefined references to arc4random
- Issue #767 - How to create a character array using json-c
- Issue #768 - commits from May 30, 2022 killed my docker build process
- Issue #769 - Issue #768
- Issue #770 - json_parse.c:170:13: error: this statement may fall through
- Issue #771 - fix fallthough warning
- Issue #772 - add JSON_C_TO_STRING_COLOR option
- Issue #773 - problem with u_int64_t
- Issue #774 - The function add_compile_options was added to CMake version 2.8.12 and later but your minimum is 2.8 which will not work
- Issue #775 - list(TRANSFORM ...) is not available prior to CMake 3.12.
- Issue #776 - Fix typo
- Issue #777 - Don't try to change locale when libc only supports the C locale
- Issue #778 - Do not insert newlines when converting empty arrays to json string and JSON_C_TO_STRING_PRETTY is used
- Issue #779 - Fix compiling for Android
- Issue #780 - Memory Leak when setting empty strings when c_string.pdata is used
- Issue #781 - Fix memory leak with emtpy strings in json_object_set_string
- Issue #782 - Fix typos found by codespell
- Issue #783 - Fix build with clang-15+
- Issue #784 - get_time_seed(): silence warning emitted by Coverity Scan static analyzer
- Issue #786 - ghpages update was not published for json-c-0.16
- Issue #787 - -static linker flag result in building failed
- Issue #788 - Clear sensitive information.
- Issue #789 - Unnecessary struct declaration and unsafe function usage
- Issue #790 - Small update to README file
- Issue #791 - json_object_object_foreach not ISO-C compliant
- Issue #792 - `json_object_get_int` does not set `EINVAL` on invalid string
- Issue #794 - replaced
- Issue #796 - Added Test for get int functions
- Issue #797 - make uninstall
- Issue #798 - API to deal with enums is missing
- Issue #799 - json_object_put: Assertion ‘jso->_ref_count > 0’ failed.
- Issue #800 - String converted to scientific notation
- Issue #801 - #error You do not have strncasecmp on your system.
- Issue #802 - Problem: modern CMake warns about version 2.8
- Issue #803 - Problem: confusing error message in snprintf_compat.h
- Issue #804 - Problem: cmake 3.25.1 warns about CMP0042 not being set
- Issue #806 - The problem is libjson-c.dylib incompatible with OS version
- Issue #807 - json simple parse syntax
- Issue #808 - iOS Build using cmake fails due to 64 to 32bits conversion precision loss
- Issue #809 - Feature request json_object_new_uint()
- Issue #810 - docs: update to Internet Standard reference
- Issue #811 - dependence on execution character set
- Issue #812 - Duplicate symbol when compiling with clang-cl
- Issue #813 - Build apps only in project itself.
- Issue #814 - Code execution order
- Issue #816 - Hi I need to generate libjson-c.so.3 and libjson-c.so.3.0.1, please help with steps
- Issue #818 - error: a function declaration without a prototype is deprecated in all versions of C
- Issue #819 - build with intel 2023 fails on vasprintf
- Issue #820 - ISO C forbids in
- Issue #821 - Any release planing for 0.17?
- Issue #822 - Added option to disable app build
- Issue #823 - Symbol not found during linking stage of libjson-c.so