History

Torsten Ruger f1a7993b47 bit of renaming , cleaning and documentation		2014-04-25 13:29:12 +03:00
..
copied_parser.rb	copied thnad to get a kickstart	2014-04-24 15:43:20 +03:00
nodes.rb	removed the structs (code smell)	2014-04-24 17:38:06 +03:00
parser.rb	fixed root	2014-04-24 21:02:27 +03:00
README.markdown	bit of renaming , cleaning and documentation	2014-04-25 13:29:12 +03:00
transform.rb	removed the structs (code smell)	2014-04-24 17:38:06 +03:00

README.markdown

Parser

This includes the parser and generated ast.

Parslet is really great in that it:

does not generate code but instean gives a clean dsl to define a grammar
uses ruby modules so one can split the grammars up
has a seperate tranform stage to generate an ast layer

Especially the last point is great. Since it is seperate it does not clutter up the actual grammar. And it can generate a layer that has no links to the actual parser anymore, thus saving/automating a complete tranformation process.

Virtual Machine

This is the logic that uses the generated ast to produce code, using the asm layer.

Apart from shuffeling things around from one layer to the other, it keeps track about registers and provides the stack glue. All the stuff a compiler would usually do.

Also all syscalls are abstracted as functions.