Guides
This section complements the generated API reference with prose documentation.
It explains the project in narrative form: what the library is for, how to build and test it, and how the generic container and ownership model works in practice.
Included Topics
- Project overview and intended use.
- Build and test workflow for local development.
- Macro-based generic containers and ownership semantics.
- Planned refactor work around fallible APIs, allocator-backed containers, and
Must...wrappers. - Working with directed graphs for reachability, CFG, and dependency-style analysis.
- Parsing simple key-value configuration files with
KvConfig.
Extending IO with User-Defined Types
Make WriteFmt and StrReadFmt work with your own struct.
June 3, 2026
Allocator Design: Bitmaps over Freelists
Why MisraStdC's allocator uses a bitmap instead of a freelist, and which bug class that removes.
May 18, 2026
Scope-Based Allocator Discipline
Use Scope blocks to give your containers an allocator with a clean lifetime.
May 14, 2026
Fallible APIs and Allocators: the design
Where the library draws the line between a caller bug and a runtime failure.
May 12, 2026
Generic Containers and Ownership
Type-parameterized containers in MisraStdC, and the L vs R insertion forms.
April 19, 2026
Why MisraStdC Exists
What the library is trying to do, what it is not, and why the project leans into generic C APIs.
April 19, 2026