This repository is old. It has been officially moved to https://git.tebibyte.media/arf/arf!
This repository has been archived on 2022-08-30. You can view files and clone it, but cannot push or open issues or pull requests.
Go to file
Sasha Koshka 3a3c588023 Added data test 2022-08-15 14:23:53 -04:00
arfc Replaced all occurences of github.com with git.tebibyte.media 2022-08-12 10:21:36 -05:00
examples Initial commit 2022-08-03 11:09:00 -04:00
file Lexer tokens are now created by the lexer 2022-08-12 14:34:07 -05:00
lexer Token kind values can now be described 2022-08-12 16:30:32 -05:00
parser Added data test 2022-08-15 14:23:53 -04:00
tests Added ToString methods for syntax tree nodes 2022-08-15 14:04:57 -04:00
types Added ToString methods for syntax tree nodes 2022-08-15 14:04:57 -04:00
.gitignore Added gitignore 2022-08-08 03:08:20 -04:00
LICENSE Added licesnse 2022-08-09 01:02:03 -04:00
README.md Add some more guidelines to readme 2022-08-12 20:32:58 -04:00
go.mod Replaced all occurences of github.com with git.tebibyte.media 2022-08-12 10:21:36 -05:00
main.go Replaced all occurences of github.com with git.tebibyte.media 2022-08-12 10:21:36 -05:00

README.md

ARF

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).

Design aspects

These are some design goals that I have followed/am following:

  • The standard library will be fully optional, and decoupled from the language
  • The language itself must be extremely simple
  • Language features must be immutable (no reflection or operator overloading)
  • Prefer static over dynamic
  • Data must be immutable by default
  • Memory not on the stack must be allocated and freed manually
  • Language syntax must have zero ambiguity
  • The compiler should not generate new functions or complex logic that the user has not written

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