-
Notifications
You must be signed in to change notification settings - Fork 31
Open
Description
I'd like to propose replacing yajl with something maintained and more future proof. It looks like we can choose from:
- mu_json
- JSON_checker
- YAJL
- LibU
- json-c
- json-parser
- jsonsl
- WJElement
- M's JSON parser
- cJSON
- Jansson
- jsmn
- parson
- ujson4c
- frozen
- microjson
- mjson
- progbase
- lwjson
- cisson
- nanoJSONc
While projects like json-c seem to be great from a functional perspective, it looks like the rely on CMake, which is not the build system used for this project. Do we have any preference?
Generally I'd like to propose to introduce the new dependency and replace yajl step by step to avoid introducing regressions. This means that we have two JSON libraries in place for a while until we remove it completely from the code.
Would that work?
Metadata
Metadata
Assignees
Labels
No labels