FFI
Froth’s FFI is intentionally narrow. It exists to expose hardware and native services without turning the language into raw C.
Use these pages in order:
- How FFI Works for the runtime model and the C authoring surface
- Project FFI for the manifest-driven build path
- Board FFI Example for an end-to-end maintained-board example
- Project FFI Example for a complete project-local binding example
The public project FFI C surface uses froth_* and FROTH_* names. Internal
runtime files may still use implementation names that are not part of the user
contract.
- How FFI Works How C functions become ordinary Froth words.
- Project FFI How project-local C bindings are declared, built, and registered.
- Board FFI Example How maintained board bindings become Froth words and wrappers.
- Project FFI Example A complete project-local FFI example with manifest, C, and Froth code.