AeroFyl for Visual Studio Code
Language support for AeroFyl, a systems-programming language with C-style syntax. This extension recognizes .fyl source files and uses the AeroFyl specification as its highlighting source of truth.
Included support
- AeroFyl language registration for
.fyl files
- Theme-aware TextMate syntax highlighting for documented declarations, types, literals, strings, interpolated
\f"..." output literals, characters, escapes, imports (use/using), members, calls, operators, punctuation, comments, structs, enums, and namespace blocks
- Highlighting for
std.io (println, eprint, eprintln), std.fs (readFile, writeFile, readBytes, writeBytes, exists), std.os (process member path), and builtin calls (exit, some, none, reference)
- Standard editor behavior for
// and /* ... */ comments, brackets, auto-closing pairs, and C-style brace indentation
- The unmodified official AeroFyl logo for language and Marketplace branding
This extension does not provide IntelliSense, completion, diagnostics, formatting, compilation, go-to-definition, or an LSP. Richer tooling such as an AeroFyl Language Server may be added later.
Development install
- Open this folder in VS Code.
- Select Run AeroFyl Language Support and press
F5 to launch an Extension Development Host.
- Open
examples/example.fyl; VS Code should select AeroFyl automatically.
The included fixture exercises documented syntax and is useful for checking your active color theme.
Package and install
npm install
npm run validate
npm test
npm run package
npm run package invokes vsce package --no-dependencies; the extension has no runtime dependencies, and this keeps development-only tooling out of the .vsix. Install the generated aerofyl-<version>.vsix with code --install-extension.
The publisher in package.json is deliberately set for the current release flow. Replace it only if you are publishing under a different Marketplace publisher account.
Highlighting limits
TextMate grammars tokenize text with regular expressions; they do not parse or type-check a whole program. As a result, semantic distinctions that depend on declarations in another file (for example, every user-defined type or enum variant) are highlighted where the local syntax makes them practical, not guaranteed in every context.
References
| |
