Skip to content

History / Multi file Projects

Revisions

  • Multi-file Projects: --project compile_commands.json is the primary flow The page described only the old single-file #include-everything convention. Now: the project driver (--project, implicit .json manifest, standard compilation-database format from CMake/bear), -l linking, multi-TU native executables (madc --project db.json -o app), with the SMAUG 51-TU example — and #include composition demoted to the lightweight alternative it is. Example verified against bin/madc v0.38.0 in all three lanes (JIT, implicit json, native). Home doc-index line updated to match. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

    @derekbsnider derekbsnider committed Jul 23, 2026
    dc4cf4c

  • Replace SMAUG-specific example with generic project in Multi-file Projects

    @derekbsnider derekbsnider committed May 19, 2026
    2b8a522

  • Initial wiki: 28 pages — Home, language guide, namespaces, reference Home page with "C, unbound." tagline, use-case cards (Script it / Ship it / Embed it), features section, and full wiki navigation. Language guide: Getting Started, Installation, Your First Program, Data Types, Control Flow, Functions, Structs & Classes, Strings & I/O, Pointers & Arrays, Modern Features, Multi-file Projects. Namespace pages: Overview + prefer, php::, perl::, python::, ruby::, js::, rust::, consolidated Namespace Reference. Advanced: Preprocessor, Embedded Headers, C23 Features, Regex, GCC Compatibility. Reference: CLI Reference, Native Executables, Embedding Guide.

    @derekbsnider derekbsnider committed May 19, 2026
    7b01ec3