cparse ships as source. 1.1.0 is the first public release — previously cparse lived only as an embedded dependency of downstream projects (fson, UMTSM), with no standalone distribution point.

Releases

VersionDateSourceChecksums
1.1.02026-09.tar.gz · .zip.tar.gz.sha256 · .zip.sha256

Each archive contains the full source tree — headers, implementation, tests, CMake build files, the Conan recipe, and the license. Extract and follow the installation guide; nothing beyond a C++20 compiler and CMake 3.20+ is required to build it.

Binary packages (.deb, .rpm) are on the roadmap but need a proper APT/YUM repository to be useful — that infrastructure will land in a later ffs component. The CMake tree already produces both locally via CPack (cpack -G DEB or -G RPM in a standalone build directory), the same way it produces the API reference's docs target.

Verifying a download

sha256sum -c cparse-1.1.0.tar.gz.sha256
# cparse-1.1.0.tar.gz: OK

Then extract and follow the installation guide.

Release notes

1.1.0 — first public release. The library as it stands after the consumers that motivated it (fson, UMTSM): Cursor (stream position, line/column tracking, save/restore), Parser (recursive-descent driver, error collection), Generator and Indentation (code-generation helpers). Two things worth calling out for anyone updating from an embedded copy:

  • Truncated input is now detected. Parser gained an opt-in open-scope counter (enterScope() / leaveScope() / openScopeDepth(), see Reference › Parser › enterScope) so a grammar with nesting can tell a clean end-of-input from one that landed mid-construct — a file cut short at a member boundary used to load as valid with the missing half silently defaulted. Purely additive: a grammar that never calls these behaves exactly as before.
  • A generated API reference (Doxygen — class diagrams, per-function call/caller graphs, header dependency graphs) now ships alongside the hand-written Reference Manual.

See also

  • Installation — how to build and integrate cparse once you have the source.
  • API Documentation — the generated reference.
  • Impressum — contact information.
  • Blog — release announcements are posted here as they happen.