The cparse project has its own home on the web starting today, at cparse.fedem.eu. Until now, cparse has lived as an embedded dependency of two projects that use it — fson for parsing FSON documents, and UMTSM for generating state-machine C++ — without any public-facing presence of its own. It has always been a small library, easy to embed and easy to forget. Giving it a site is a step towards taking it seriously as a standalone component.
What is here today
The site is deliberately modest at launch:
- An installation guide covering all three integration paths:
add_subdirectoryfor host CMake projects, a standalone system install exposed viapkg-config, and a Conan recipe for consumers already on that dependency manager. - A Getting Started walkthrough that builds a working comma-separated-integer parser in under fifty lines of code.
- A reference manual with one page per public class, alongside a link to the full Doxygen tree.
- A small examples gallery with three self-contained toy grammars.
- The Downloads page for the current source archive with SHA-256 checksums.
What is next
Several things are already on the roadmap and will land here as they happen:
- Deeper user-guide sections on grammar patterns (cursor save/restore,
enterScope/leaveScope, streaming from strings) and on the code-generation helpers. The first drafts exist; they need to be reviewed against real grammar-writing sessions rather than synthetic ones. - A proper release management page. For now, downloads are a hand-maintained table. This will move to structured metadata so checksum, signature and release-note information stays in one place.
- In-site source browsing. Because the cparse source is not on a public repository, the site itself will eventually let you browse the code — statically at first, then with commit history and version navigation.
- Binary packages (
.deb,.rpm) served from a proper APT and YUM repository. The CMake tree can already produce them; the piece that is missing is the repository infrastructure that letsapt-get install cparsework.
Why publish this now
The library is stable — the API has not changed in over a year and the version has stayed at 1.0.1 through steady use in two production consumers. What has been missing is an on-ramp for anyone else who might want to write a small grammar in C++ without hand-rolling the cursor and error-collection machinery. This site is that on-ramp.
If you use cparse in a project of your own, drop a note via the contact page — I would like to know.

