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 09706ef7f3 Commented out some things in func test case
Apparently, cBasicPhrases is somehow causing the mysterious nil
tree bug. this will be investigated further soon.
2022-09-01 21:38:50 -04:00
arfc Fixed import paths 2022-08-30 01:11:10 -04:00
assets Added progress heatmap 2022-08-25 00:51:54 -04:00
examples Fixed parsing of interface section behaviors 2022-08-24 00:25:52 -04:00
file Error widths now work properly 2022-08-18 02:04:49 -04:00
infoerr Fixed import paths 2022-08-30 01:11:10 -04:00
lexer Bit shift assignment tokens now have correct width 2022-08-30 01:35:40 -04:00
parser Test logs error even if tree is nil 2022-09-01 21:37:15 -04:00
tests Commented out some things in func test case 2022-09-01 21:38:50 -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 Fixed import paths 2022-08-30 01:11:10 -04:00
LICENSE Added licesnse 2022-08-09 01:02:03 -04:00
README.md Added progress heatmap 2022-08-25 00:51:54 -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

Compiler Progress

Progress heatmap
  • Yellow: needs to be completed for the MVP
  • Lime: ongoing progress in this area
  • Green: Already completed