This string output type replaces all non printable bytes (00-07, 0b, 0e-1f, 7f-ff) to "\u00xx" sequences. This allows json decoders to reconstruct binary string without interpreting binary sequences as Unicode characters.

See test cases at:

https://github.com/dsvensson/libjson/commit/b17efbf00817fac3aa0aab46a734da3db2c42794

This works fine in both Chrome and Python, and should probably be supported for completeness sake.

Given the input {"t":true,, the parser (json_parser_string(...)) would tell me that an error had occurred and give me the invalid error code 32767. Initializing int ret to zero in do_action(...) seems to fix the problem.

HI, Small, clever, good performace, event driven, and I like it. json string to struct is good, so i do some work to enhance c struct to json string.

I fork at https://github.com/zhaozg/libjson, add jsondom.c and jsondom.h code, some hack on json-dom api. Hope this will make you think about a more easy way for construct json-dom from c api. Thanks.

MediaTags uses libjson for converting id3tags to JSON.

However, the output isn't parseable and doesn't pass JSONLint.com

See gist: https://gist.github.com/733715

(Continuing the discussion from issue #3)

which part of the actions_map table MSVC is complaining about ? is it the function pointer or the array initilizer that it thinks is non-constant ?

I'm not entirely sure that I've got the terminology exactly right, but MSVC does not implement what I think might be called designated array initializers:

int a[3] = {
    [1] = 5,
    [0] = 7
};

The [1] =-part throws MSVC completely off. This seems incredible, since this syntax is a part of C99, but MSVC does not claim to implement C99 :(

Currently, they are trying to implement C++0x, and anything from C99 that's included in C++0x will be ported to the C-compiler. Unfortunately this syntax has not been included and is not on the roadmap for MSVC.

I'd be happy to help getting libjson working on MSVC, but I'm not entirely sure what might be the best solution for this exact problem. Any thoughts?

Hi, I want to reuse your likely open-source json parser in the my closed-souce program. I wanted to check whether your license allows me to do that but suddenly found out there's no any license at all. Please indicate which license is applicable. If you are not aware baout details of the open-sorce licenses, you probably need to read here more - https://opensource.org/licenses I recommed new BSD 3-clause license or MIT licsnse - this allows code to be compiled into program statically, on the constast LGPL allows only dynamic linking of the closed-source and open-souce code. Please indicate your choise of license by addin file with license text to repository. Thank you in advance...

The two first patches fix a non-logical thing : casting an unsigned as a signed to compare it with unsigned. The third one is more a warning fix : as the 'printer' parameter is unused. Then I chose to reset it. The last one is to remove an unused trailing white space (you can ignore this one).

Hi Vincent,

I ended up compiling your json.c & json.h files using the Sun Studio compiler - which threw up warnings about having '-1' as an unsigned 8bit int in the hextable.

Simple fix is to convert all the -1's to 255 (0xFF) within the hextable (as that's what GCC treats them as anyway).

That's it, no other warnings or errors were generated.

Thanks!

Iain.

Unfortunately, libjson does not compile with MS's C compiler :(

These commits fix some of the problems. Some of the changes, for example relating to signed vs unsigned, make sense independently of MSVC, I think.

With all these changes, it still won't work in MSVC, because it does not implement support for designated initializers for arrays :( This does not seem to be on the roadmap for MSVC either, unfortunately.

Even though it still won't work in MSVC, I find it valuable to deviate as little as possible from what works on the greatest amount of compilers. Pull what you feel like, and disregard the rest, no stress :)

If the actions_map could easily be initialized in an MSVC-friendly way, I would be very grateful. I'm a bit scared of that table myself, so I don't know quite where to start if I were to change it :) I've implemented initializing it at runtime as a test, and with that final change it works nicely in MSVC.

A bug in memory reallocation caused stack growth past the initial size to result in a heap buffer overflow. This changes the memory_realloc call in dom_push to allocate newsize elements instead of newsize bytes.

This appears to fix issue #20.

Thanks for the library. I'm now using it to load and save configuration files in an IoT Linux service.

I have made some small additions I think you will find useful (feel free to disregard if not!):

1. Add function json_strerror. Takes an int return value from any other function in the library and returns a const char* of the human-readable error message for that code (or '<unknown>' if it isn't a known error code).
2. Add function json_perror. Calls json_strerror and outputs the message to stderr.

All of my changes can be disabled by uncommenting the #define JSON_NO_ERRORMSG line I added to json.h. I did this in case memory constraints are a concern.

These functions are intended to be in the spirit of the POSIX strerror and perror functions.

Cheers, Ryan

I added the following features to the library (mostly related to event based parsing mode) and since they are backward compatible with the current library API I thought it might be a good idea to merge them into upstream:

• In-place parsing mode: memory utilization required by the library does not depend anymore on the input sequence. The input buffer is leveraged to execute in-place parsing and no extra memory is allocated for this.
• Partial data callbacks: this is more like a requirement needed to implement in-place parsing mode. When this is enabled, the parser doesn't keep any internal buffer across two consecutive invocations of the parser function.
• Support for Catch framework and unit-tests: added unit tests by using Catch test framework
• Very small refactoring.

To Do:

• Documentation needs to be updated in case you decide to merge these features.

Cheers, Francesco

Hi,

I get the following warnings when compiling with -Wsign-compare:

json.c: In function ‘json_print_args’:
json.c:965:15: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
    if (length == -1)
               ^~

jsonlint.c: In function ‘printchannel’:
jsonlint.c:48:10: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
  if (ret != length)
          ^~
jsonlint.c: In function ‘process_file’:
jsonlint.c:96:17: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
   for (i = 0; i < processed; i++) {
                 ^

Hi there

I fuzzed libjson with American Fuzzy Lop (http://lcamtuf.coredump.cx/afl/ , for no real reason at all, I was just looking for libraries to test AFL). I was running jsonlint with:

jsonlint --tree inputfile

The inputfile with the following content will crash jsonlint (segmentation fault):

[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[ [[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[ [[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[][[[[[[[[[[[[[[

Best regards, floyd