3 ms·
The code is certainly very short, but what about \u escape sequences in strings, parsing different representations of numbers, etc.? Since those things are part
by udp 14y ago
The code is certainly very short, but what about \u escape sequences in strings, parsing different representations of numbers, etc.? Since those things are part of the JSON standard, you're not a JSON parser if you just leave them to the application to handle.
Since this skimps out on half of the work, it won't even be able to tell you with certainty what's valid JSON and what isn't.
(disclaimer: I also wrote a popular ANSI C JSON parser)
- stevelaz 14y agoI saw json-parser. Looks good. I'm currently using YAJL for a project, but I'm open to switching to something faster/easier. Have you done any performance tests against other C json parsers? Thanks,