The ARF programming language
This repository has been archived on 2024-02-27. You can view files and clone it, but cannot push or open issues or pull requests.
Go to file
Sasha Koshka c042305ebe Test commit
Trying to see if my username appears
2022-08-09 21:44:41 -04:00
arfc Added stub arfc command 2022-08-08 03:09:16 -04:00
examples Initial commit 2022-08-03 11:09:00 -04:00
file Added print method to error 2022-08-09 20:12:33 -04:00
lexer Test commit 2022-08-09 21:44:41 -04:00
.gitignore Added gitignore 2022-08-08 03:08:20 -04:00
go.mod Initial commit 2022-08-03 11:09:00 -04:00
LICENSE Added licesnse 2022-08-09 01:02:03 -04:00
main.go Created stub high-level module compilation function 2022-08-08 03:08:50 -04:00
README.md Added more information about the language's design to readme 2022-08-09 21:15:49 -04:00

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)
  • Data must be immutable by default
  • Memory not on the stack must be allocated and freed manually
  • Language syntax must have zero ambiguity

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