-
Notifications
You must be signed in to change notification settings - Fork 0
Comparing changes
Open a pull request
base repository: SwintonStreet/jsoncpp
base: master
head repository: open-source-parsers/jsoncpp
compare: master
- 6 commits
- 12 files changed
- 8 contributors
Commits on Nov 11, 2025
-
Fix "include what you use" issue (open-source-parsers#1625)
Fix IWYU for istreambuf_iterator. Co-authored-by: Victor Hugo Vianna Silva <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 9af09c4 - Browse repository at this point
Copy the full SHA 9af09c4View commit details
Commits on Nov 12, 2025
-
Make the build configuration under Bazel more correct. (open-source-p…
…arsers#1600) * Expose JSON_USE_EXCEPTION and JSON_HAS_INT64 as Bazel config flags with defaults that match the existing Bazel build. Switch //:jsoncpp from using copts ro defines for JSON_USE_EXCEPTION and JSON_HAS_INT64 so that rules that depend on it get the same config. Make src/test_lib_json/fuzz.cpp respect JSON_USE_EXCEPTION. * #ifdef stuff that should only be used with JSON_USE_EXCEPTION. --------- Co-authored-by: Jordan Bayles <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 6f6aca1 - Browse repository at this point
Copy the full SHA 6f6aca1View commit details -
Add Bazel tests (open-source-parsers#1601)
* Expose JSON_USE_EXCEPTION and JSON_HAS_INT64 as Bazel config flags with defaults that match the existing Bazel build. Switch //:jsoncpp from using copts ro defines for JSON_USE_EXCEPTION and JSON_HAS_INT64 so that rules that depend on it get the same config. Make src/test_lib_json/fuzz.cpp respect JSON_USE_EXCEPTION. * #ifdef stuff that should only be used with JSON_USE_EXCEPTION. * Modify runjsontests.py to allow passing a single test case file. * Add tests to the Bazel builds. * Reverse the polarity to fix a bug. --------- Co-authored-by: Jordan Bayles <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 4bcbc6a - Browse repository at this point
Copy the full SHA 4bcbc6aView commit details -
Return false in Reader::readValue when stack limit is exceeded (open-…
…source-parsers#1619) jsoncpp, as a shared library, should not call `abort` merely because there's an error reading a value. See https://en.cppreference.com/w/c/program/abort, `abort` should only be called to **abnormally** cause the program to exit. Functions inserted by `atexit` are also not called, meaning that the host program may have not cleaned up resources properly. But here, exceeding stack limit isn't a sign of abnormalty. `exit` is not a good substitute either, see the `exit-in-shared-library` from Debian: https://lintian.debian.org/tags/exit-in-shared-library.html Fix open-source-parsers#1618 In this case, returning false seems like a better idea. Co-authored-by: Jordan Bayles <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 30e7528 - Browse repository at this point
Copy the full SHA 30e7528View commit details -
Remove deprecated/removed clang-tidy key AnalyzeTemporaryDtors (open-…
…source-parsers#1614) (open-source-parsers#1615) Co-authored-by: Ben Magistro <[email protected]> Co-authored-by: Jordan Bayles <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for e16663c - Browse repository at this point
Copy the full SHA e16663cView commit details -
[docs] Consuming JSONCpp via Conan package manager (open-source-parse…
…rs#1622) * Fix Conan badge URL Signed-off-by: Uilian Ries <[email protected]> * Add Conan instructions in README Signed-off-by: Uilian Ries <[email protected]> * Add build missing Signed-off-by: Uilian Ries <[email protected]> --------- Signed-off-by: Uilian Ries <[email protected]> Co-authored-by: Jordan Bayles <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for b511d9e - Browse repository at this point
Copy the full SHA b511d9eView commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff master...master