Difference between revisions of "Yet Another JSON Library (YAJL)"
(Created page with "{{Entry |Name=Yet Another JSON Library (YAJL) |Short description=a small event-driven (SAX-style) JSON parser written in ANSI C, and a small validating JSON generator. |Full desc...") |
(No difference)
|
Latest revision as of 09:10, 12 April 2011
Yet Another JSON Library (YAJL)
http://lloyd.github.com/yajl/
a small event-driven (SAX-style) JSON parser written in ANSI C, and a small validating JSON generator.
Why does the world need another C library for parsing JSON? Good question. In a review of current C JSON parsing libraries I was unable to find one that satisfies my requirements. Those are:
- 0. written in C
- 1. portable
- 2. robust -- as close to "crash proof" as possible
- 3. data representation independent
- 4. fast
- 5. generates verbose, useful error messages including context of where the error occurs in the input text.
- 6. can parse JSON data off a stream, incrementally
- 7. simple to use
- 8. tiny
- Numbers 3, 5, 6, and 7 where particularly hard to find, and were what caused me to ultimately create YAJL.
Licensing
License
Verified by
Verified on
Notes
Leaders and contributors
| Contact(s) | Role |
|---|---|
| Lloyd Hilaiel | Maintainer |
Resources and communication
| Audience | Resource type | URI |
|---|---|---|
| Developer | Homepage | http://github.com/lloyd/yajl |
| General | Mailing List Subscribe | mailto:yajl@librelist.com |
Software prerequisites
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the page “GNU Free Documentation License”.
The copyright and license notices on this page only apply to the text on this page. Any software or copyright-licenses or other similar notices described in this text has its own copyright notice and license, which can usually be found in the distribution or license text itself.