Evaluate

A homemade professional compiled programming language.

It compiles to NASM and can cross-compile, though it's cross-compilation capabilities haven't been verified.

Example program

Input

Int_64 number = 123456751
printf("num", "{number}\n")

Result: 123456751

Input:

equate("myEquation", "240*4")

Result: 840

Syntax guide has moved to GitHub discussions.

Installation

1. Install NASM (The Netwide Assembler) and GNU Binutils on your desired computer. These are Evaluate's external dependencies.
2. If you're using Visual Studio Code, the Evaluate Language Support extension is recommended.
3. If it exists, download the Evaluate binary for your OS. If not, then build from source:

Build from source

1. Install GNU Make. Make sure to add to PATH or envrionment variables.
2. Install Node.js and npm (www.nodejs.org). Make sure to select npm when given the option by the node installer. Make sure to add to PATH or environment variables.
3. Install the latest release of NASM (the Netwide Assembler) for your OS. Make sure to add to PATH or environment variables.
4. If you're using Visual Studio Code, the Evaluate Language Support extension is recommended.
5. Follow the instructions below for your OS.

Windows

Run make win, the output will be a .exe file

Unix (macos/linux)

Run make unix, the output will be an executable

MacOS app

Run make macosapp, the output will be a .app file

Run

1. Template: evaluate <input> [args]

CLI Flags:

--input <file> -i <file> - Path to the target file - Default parameter
--verbose -v - Outputs stack modifications
--version - Version of Evaluate installation
--force -f - Forces the program to run
--disable-warnings - Do not show warnings
--output <output> -o <output> - defaults to "output" - The name of the outputted *.asm file.
--help -h - Outputs the args help menu

1. Use NASM to compile the generated asm file. The OS-specific commands are:

Linux (highly supported): nasm -f elf <file>.asm
Windows (supported): nasm -f win32 <file>.asm
MacOS (not supported): nasm -f macho64 <file>.asm

1. Link the object file (GCC can also be used).

Linux and MacOS: ld -o <file> <file>.o
Windows: ld -o <file>.exe <file>.o

Git

As you might have noticed, we have multiple GitHub branches. The order of reliability follows:

1. Featured Experiments (branches starting with "EVAL", this is a Jira ID)
2. Experimental Build (main)
3. PTB - Public Test Build
4. Production

with 1 being the least reliable and littered with bugs and 4 being the most reliable and without many bugs. To run anything other than production, you must use the --force flag.