The ARF programming language
Sasha Koshka
5d27befb6f
Previously, relative require paths would be resolved based on the current working directory. They are now resolved based on the path of the module. |
||
|---|---|---|
| analyzer | ||
| arfc | ||
| assets | ||
| examples | ||
| file | ||
| infoerr | ||
| lexer | ||
| parser | ||
| testCommon | ||
| tests | ||
| translator | ||
| types | ||
| .editorconfig | ||
| .gitignore | ||
| go.mod | ||
| LICENSE | ||
| README.md | ||
The ARF programming language.
This is still under development and does not compile things yet. Once complete, it will serve as a temporary compiler that will be used to write a new one using the language itself.
The old repository can be found here.
ARF is a low level language with a focus on organization, modularization, and code clarity. Behind it's avant-garde syntax, its basically just a more refined version of C.
A directory of ARF files is called a module, and modules will compile to object files (one per module) using C as an intermediate language (maybe LLVM IR in the future).
Be sure to visit the wiki for more information.
Planned Features
- Type definition through inheritence
- Struct member functions
- Go-style interfaces
- Generics
- A standard library (that can be dynamically linked)
Checklist
- File reader
- File -> tokens
- Tokens -> syntax tree
- Syntax tree -> semantic tree
- Semantic tree -> C -> object file
- Figure out HOW to implement generics
- Create a standard library
Compiler Progress
- Yellow: needs to be completed for the MVP
- Lime: ongoing progress in this area
- Green: Already completed