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 78b8b9dacd Fixed test case for parser
The correct output string was missing a type specifier. The lexer now passes
this test.
2022-08-19 11:37:30 -04:00
arfc Replaced all occurences of github.com with git.tebibyte.media 2022-08-12 10:21:36 -05:00
assets Added logo to README 2022-08-17 20:16:48 -04:00
examples Initial commit 2022-08-03 11:09:00 -04:00
file Error widths now work properly 2022-08-18 02:04:49 -04:00
infoerr Error widths now work properly 2022-08-18 02:04:49 -04:00
lexer Changed permission codes to only determine private/public/readonly 2022-08-18 12:09:17 -04:00
parser Fixed test case for parser 2022-08-19 11:37:30 -04:00
tests Fixed test formatting 2022-08-19 03:05:25 -04:00
types Changed permission codes to only determine private/public/readonly 2022-08-18 12:09:17 -04:00
.gitignore Added gitignore 2022-08-08 03:08:20 -04:00
go.mod Replaced all occurences of github.com with git.tebibyte.media 2022-08-12 10:21:36 -05:00
LICENSE Added licesnse 2022-08-09 01:02:03 -04:00
main.go Replaced all occurences of github.com with git.tebibyte.media 2022-08-12 10:21:36 -05:00
README.md Remove line break at top of readme 2022-08-17 21:48:06 -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)
  • 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
  • One line at a time - the language's syntax should encourage writing code that flows vertically and not horizontally, with minimal nesting

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