finds.dev

abhilashkrishnan/blaze

Blaze Programming Language

View on GitHub

CApache-2.0updated Jun 2023

// the take

Blaze is a C project for an object-oriented language that would compile to bytecode and run on its own virtual machine. The README states the plan in future tense and shows no syntax, so the file tree is the only evidence of what exists: a scanner, a compiler, chunk and value layers, an object module, a memory module, and a VM. It is for someone who wants to read a small language implementation, not for anyone hoping to write Blaze programs.

- The module split follows the usual bytecode VM layout. The scanner, compiler, chunk, value, object, memory, and VM each sit in their own directory with a header, so a single stage can be read in isolation.

- debug.c beside the VM points to a bytecode disassembler, which is the first tool you want when the compiler emits wrong output.

- It ships a Makefile, a LICENSE, and a .gitignore, so it can be built and forked without guessing the project setup.

- The README is all future tense. It names no syntax, no types, no example program, and no feature that works today, so there is nothing to run.

- The last push was June 2023, with zero stars and zero forks. It reads as stalled.

- The README calls object orientation the main feature, but the tree shows only a generic object.c. Classes, methods, and inheritance have no visible home yet.

- There are no build or run instructions beyond the file list and no tests directory. Whether the Makefile produces a working binary can't be judged from what's here.

We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →

// at a glance

Stars
0
Forks
0
Language
C
License
Apache-2.0
Last commit
17 Jun 2023

// nearby

If blaze isn't quite it.

All repos →