Documentation

A small JSON component with a clear boundary.

Jsonic++ is the independent home of the JSON implementation used by Nift and Minify++. The public surface is intentionally boring: one header, one JSON value type, explicit parse errors, ordinary C++ containers underneath, and no runtime dependency graph.

Design goal: correct JSON parsing and useful value access without pulling a large serialization ecosystem—or unrelated formats and application policy—into your program.

Learn the library

Getting started goes from vendoring the header through parse, inspection, construction and serialization. API is the detailed reference for every public operation and the six JSON value kinds. Architecture explains the owning value model and why the implementation deliberately stays small.

Understand the guarantees

Contracts describes syntax, object, Unicode, number, round-trip and synchronization guarantees. Battle tested explains the executable evidence behind those claims, Memory & resource safety records the completed standalone sanitizer/RSS/Valgrind lifetime gate, while Production readiness separates that maintained evidence and downstream dogfooding from what a young standalone library still needs to earn.

Decide whether it fits

Comparisons contrasts Jsonic++ with mature C++ JSON libraries by strengths, weaknesses and design boundary rather than pretending one parser is universally best. Developer experience explains the human/AI maintenance model.

Where it came from

The parser was not invented for a standalone branding exercise. It was extracted from a byte-identical implementation already exercised by Nift core and Minify++. Jsonic++ now owns parser semantics independently; those projects continue to vendor synchronized copies. That history is useful evidence, but the standalone project is also expected to build its own conformance, fuzzing and downstream-user history.

What you will not find here

Jsonic++ does not try to become a universal serialization layer. There is no reflection framework, ORM-style mapping system, JSON query language, schema engine, networking API or collection of unrelated formats. If your project needs those facilities, the comparison guide points toward libraries with deliberately larger scopes.