Runtime Library and Generated Wrappers
Reference: This page is a source-based technical synthesis of the LaTeX chapter cited below. For exact syntax, availability or ABI signatures, verify the versioned source, manifest and executable tests.
Scope and source boundary
Generated wrappers implement the versioned ABI surface; check generated artifacts rather than reverse-engineering internal class names.
Generated bindings are an adapter over versioned runtime operations and ABI types. The .NET sources describe generation, typed wrappers, manifest certification and compatibility checks. Application code should prefer generated types and use untyped call descriptors only where the public contract explicitly requires them.
Engineering rules
- Generate from the exact published contract and record its version.
- Inspect type, nullability, argument direction and ownership mappings.
- Prefer strongly typed wrappers when provided by the generated package.
- Test binding upgrades and reject undocumented compatibility assumptions.
Chapter outline (original LaTeX headings)
- Export pipeline
- Example command shape
LaTeX provenance
Primary chapter: Runtime/logiCells Runtime Programming for .NET/binding-generation-workflow.tex.