DOCUMENTATION · V81 EDITION
nC documentation.
Usage and architecture reference: syntax, memory, IR, ABI, linking and native compiler reconstruction.
CONTINUE READING→Why nC exists
A program runs on a concrete machine. Between source and execution, the toolchain chooses data layouts, calling conventions, memory operatio…
Reading the project
The language is nC; the compiler is ncc. Ordinary source uses `.n`. Machine modules also use `.nm`, and primitive examples use `.ncp`.…
Setting up the toolchain
Download the V81 native kit from the repository's Releases page. It contains the compiler, runtime provider, examples and SHA-256 checksums.…
The first program
The repository retains this source in `examples/00_hello/hello.n`:…
Places and functions
`value >> int <- 0;` declares a typed place and initializes its bits. `>>` separates the name and type; `<-` writes a value. A declaration w…
Memory and services
Ordinary nC source has manual/raw memory semantics. Type checking does not add automatic release, ownership tracking or pointer-lifetime val…
The machine layer
`[@machine]` participates in the same typed system. Registers, labels, instructions and terminators carry contracts that must remain coheren…
Working during bootstrap
Record the complete command, host, target, executable digest, provider, minimal source and diagnostic for each reproduction. When comparing …
Contracts between levels
nC exposes several ways to express a program within one semantic model. Ordinary source, the foundational root, machine code and primitives …
Parser AST semantics and IR
The parser recognizes compact imports such as `use <io:output>;`, named containers, sections and grouped functions. Material V2 tests in `cr…
Machine code and control flow
`[@machine]` represents instructions with typed structure. Operands, registers, labels and terminators must remain coherent from parsing thr…
Memory and representation
Ordinary source retains a manual/raw contract. The compiler does not introduce ownership, general bounds checks, automatic pointer-lifetime …
Materialization ABI and linking
MCT participates in object and image generation. The backend translates program decisions into target-compatible bytes and metadata. Linking…
What bootstrap V81 demonstrates
The V81 dossier records four final reconstructions: B2 and C2 on Windows, and B2 and C2 on Linux/WSL. Each rebuilds 74 units in a new direct…
Reproducing and reviewing evidence
`bootstrap/frontend-v81-build.json` fixes reconstruction sources. Builders verify SHA-256 during copying and reject destinations containing …
Releases and contributions
A release needs an executable entry path: purpose, requirements, a program, expected output and an issue channel. Packages identify their ed…
No chapters match that term. Try another word.
Repository references
Technical references describe subsystem surfaces and contracts. Check support claims against their fixtures and profile evidence.