Classic BASIC.
New foundations.
A modern compiler and runtime for Amiga GFA BASIC 3.5 — researched carefully, built in Rust, and designed for native Linux executables.
Implementation dashboard.
A source-linked snapshot of what exists today and what remains planned. Research, prototypes and supported implementation are deliberately kept separate.
Implemented 3.5 addendum API
Explicitly documented interpreter declarations from the Amiga 3.5 addendum only; includes language-core and Amiga platform declarations. Excludes inherited 3.0 base-manual features, editor-only changes, compiler-only features, and Atari ST declarations. This is a confirmed addendum subset, not the complete Amiga GFA BASIC 3.5 language API.
Roadmap progress
Implementation states
Compiler frontend prototype
PrototypeThe frontend accepts only the documented FACT, VARIAT and COMBIN assignments followed by PRINT; it is not a general GFA BASIC parser.
Typed project IR
PrototypeTyped IR construction and verification exist for the narrow prototype; the general semantic and lowering contract is not implemented.
General language semantics
ResearchVersion-specific language rules remain evidence-gated; research and candidate corpus entries are not implementation.
Compiler CLI
PartialHelp, version, the subset formatter and the narrow prototype build command exist; project loading, general checking and production compilation do not.
Source formatter
PartialFormatting is implemented only for syntax accepted by the current frontend; unsupported constructs are rejected.
Language server
PartialThe dependency-free LSP adapter supports document lifecycle and shared-frontend diagnostics; formatting, navigation, completion and rename are not implemented.
LLVM backend
PlannedLLVM is the intended production backend; no LLVM backend implementation or binding is selected.
Generated-program runtime
PlannedThe runtime crate establishes an architectural placeholder; generated-program runtime behavior and a stable runtime ABI are not implemented.
Linux platform adapter
PlannedThe platform crate defines the intended adapter boundary; Linux services and SDL3 integration are not implemented.
Testing and dialect conformance
PartialUnit and prototype smoke tests plus a metadata-validated evidence corpus exist; no general corpus runner or full dialect conformance suite exists.
Release and supply-chain tooling
PartialPR SBOM validation and a release-event SBOM attachment workflow exist; compiler packaging and a complete release workflow do not.
Build-time snapshot · Source freshness is not timestamped in the current data model. Status model ↗ · Detailed roadmap ↗
Recent activity.
Recently updated
- Merged pull request[API Registry] Reconcile Amiga GFA BASIC 3.5 platform profile ↗PR #607 merged
- Commit[API Registry] Reconcile Amiga GFA BASIC 3.5 platform profile (#607) ↗Commit 55e536a
- Merged pull requestdocs: define Ghidra API analysis boundary for agents ↗PR #612 merged
- Commitdocs: define Ghidra API analysis boundary for agents (#612) ↗Commit e5813bf
- Merged pull request[Compiler] Lower typed IR from resolved semantic model ↗PR #601 merged
- Commit[Compiler] Lower typed IR from resolved semantic model (#601) ↗Commit ced5ad4
- Merged pull request[CI] Make mutation schedule guard resilient to delayed runners ↗PR #609 merged
- Commit[CI] Make mutation schedule guard resilient to delayed runners (#609) ↗Commit f020422
- Merged pull request[CI] Suppress ShellCheck false positive for Pages cleanup trap ↗PR #606 merged
- Commitci: suppress ShellCheck false positive for EXIT cleanup trap (#606) ↗Commit e591114
- Merged pull request[Testing] Validate and select versioned construct manifests (#571) ↗PR #593 merged
- Commit[Testing] Validate and select versioned construct manifests (#571) (#593) ↗Commit 7eb80ca
Last successful source fetch: · Maximum 12 items · GitHub PR merges and commits are activity events, not feature-completion claims.
CI & supply-chain health.
Build-time snapshot from GitHub Actions. Latest result and last successful run are shown separately; missing runs, stale results and unconfigured workflows are never counted as healthy.
Documentation checks
IN PROGRESSLatest: in progress · push · main · 0h ago · fresh
Last success: 2026-11-21T22:21:29Z · 0h ago · Open successful run ↗
Markdown, JavaScript, API registry, corpus metadata and local-link validation.
Rust checks
IN PROGRESSLatest: in progress · push · main · 0h ago · fresh
Last success: 2026-11-21T22:21:36Z · 0h ago · Open successful run ↗
Formatting, Clippy, workspace tests/build and formatter fixtures.
Security audit
SUCCESSLatest: success · pull_request · worker/issue-42-data-pointer-fixture · 0h ago · fresh
Last success: 2026-11-21T22:21:27Z · 0h ago · Open successful run ↗
RustSec audits for workspace, fuzz and benchmark lockfiles.
Source-loader fuzzing
SUCCESSLatest: success · pull_request · compiler/semantic-model-ir-600 · 63h ago · fresh
Last success: 2026-11-19T07:12:32Z · 63h ago · Open successful run ↗
Fuzzes the source loader only; lexer/parser fuzzing is not configured.
Benchmarks
SUCCESSLatest: success · pull_request · worker/issue-42-data-pointer-fixture · 0h ago · fresh
Last success: 2026-11-21T22:21:22Z · 0h ago · Open successful run ↗
Source-loading benchmark; pull requests validate compilation without recording measurements.
Release SBOM
SUCCESSLatest: success · pull_request · worker/issue-42-data-pointer-fixture · 0h ago · fresh
Last success: 2026-11-21T22:22:00Z · 0h ago · Open successful run ↗
Validates PR SBOMs and uploads on published releases; release attachment is unproven until a release runs.
GitHub Pages
IN PROGRESSLatest: in progress · push · main · 0h ago · fresh
Last success: 2026-11-19T07:16:19Z · 63h ago · Open successful run ↗
Builds and publishes the static production website.
Pull request preview
SUCCESSLatest: success · pull_request · worker/286-amiga-35-api-profile · 0h ago · fresh
Last success: 2026-11-21T22:23:11Z · 0h ago · Open successful run ↗
Builds and smoke-tests same-repository pull request previews.
Conformance suite
NOT CONFIGUREDNo workflow run recorded
No successful run recorded
No dedicated compiler conformance workflow is configured.
Snapshot generated 2026-11-21T22:23:13.231922Z. Freshness threshold: 168 hours. View all workflow runs ↗
Bringing a classic
language forward.
GFA BASIC was part of the creative computing era of the Amiga. This project explores a careful, evidence-led way to compile its 3.5 dialect into native programs — without pretending that the hard compatibility work is already done.
Faithful by evidence
Language rules are tied to version-specific references. Uncertain behavior stays explicitly unresolved.
Native by design
The target is Linux x86-64. LLVM is the planned production backend; the current C bridge is temporary.
Rust throughout
A modular compiler, generated-program runtime and platform layer form the planned foundation.
A small step.
A real executable.
The experimental frontend accepts a deliberately narrow, documented subset: literal FACT, VARIAT and COMBIN assignments followed by PRINT. It verifies typed project IR before using a temporary C/cc bootstrap.
x = FACT(5)
PRINT x
The current prototype demonstrates a deliberately limited subset; it is not general GFA BASIC support and does not claim compatibility with the original interpreter. Variables are limited to x, y and z, with no reassignment. Arguments must be integer literals: FACT(n) accepts 0–20, while VARIAT(n,k) and COMBIN(n,k) accept 0 ≤ k ≤ n ≤ 20. These are prototype limits, not limits of the GFA BASIC language. General language semantics, the production IR, LLVM backend and runtime remain unimplemented.
Early tools.
Explicit boundaries.
Source formatter
The gfabasic fmt library and CLI format only the currently supported FACT, VARIAT, COMBIN and PRINT syntax. Unsupported syntax is rejected; this is not yet a general GFA BASIC formatter.
Language server
The standalone LSP adapter supports document open/change/close and parser diagnostics. Formatting integration, navigation, completion and rename are not implemented.
↗Research before claims
Language rules remain evidence-gated against the Amiga 3.5 references. The implemented editor tools do not imply full language parsing or conformance.
↗Clear boundaries.
Independent layers.
The planned system separates language semantics from code generation and platform integration. Each layer can evolve without quietly changing the compatibility contract.
Compiler
Source loading, diagnostics and a narrow FACT/PRINT frontend with prototype-only typed IR. General semantic analysis and IR remain planned.
EXPERIMENTAL CORECode generation
Verified IR translated to native code through the planned LLVM backend.
PLANNED · LLVMRuntime & platform
Generated-program runtime and Linux integration, including planned SDL3 support.
PLANNEDWhat the language defines.
A generated, source-linked inventory of GFA BASIC declarations. Evidence, implementation, Linux support and conformance are shown separately; unknown and disputed behavior stays visible.
Coverage counts are independent and have explicit denominators. There is no aggregate “percent implemented”. Select an entry to open its source-linked project documentation.
Loading the generated API catalogue…
Built in deliberate stages.
Dependencies & sequencing rules
The initial dialect/version is selected (Amiga GFA BASIC interpreter 3.5); 3.0/3.03 rules remain inherited candidates until confirmed for 3.5, and feature-level source evidence still gates language semantics, parser acceptance criteria, and conformance claims.
Source manager, lexer, parser, semantic analysis and typed IR are sequential dependencies for the first compiler path.
LLVM backend and runtime integration depend on a stable typed IR and runtime ABI.
Platform APIs depend on verified profile declarations; Amiga and Atari ST evidence must not be conflated.
A user quick start and installation guide depend on a working, tested CLI and distributable build.
The generic source-loader fuzz target is implemented; lexer/parser fuzz targets depend on stable frontend entry points and source contracts.
Release packaging depends on successful end-to-end builds and explicit runtime dependency policy.
Go a little deeper.
Help shape what comes next.
Follow the work, inspect the code, or contribute to the research and implementation.