rubyx

History

Torsten Ruger adca8b21c1 move soml tests out, small cleanup		2016-12-06 15:08:29 +02:00
..
behaviour.rb	some docs	2016-12-06 11:38:09 +02:00
binary_code.rb	some docs	2016-12-06 11:38:09 +02:00
class.rb	move soml tests out, small cleanup	2016-12-06 15:08:29 +02:00
dictionary.rb	move parfait into register	2015-11-18 12:04:25 +02:00
frame.rb	fix docs for rename	2016-02-25 12:03:11 -08:00
indexed.rb	some docs	2016-12-06 11:38:09 +02:00
integer.rb	move parfait into register	2015-11-18 12:04:25 +02:00
list.rb	fix docs for rename	2016-02-25 12:03:11 -08:00
message.rb	rename layout to type	2016-02-25 11:50:10 -08:00
meta_class.rb	rename layout to type	2016-02-25 11:50:10 -08:00
method.rb	some docs	2016-12-06 11:38:09 +02:00
object.rb	move soml tests out, small cleanup	2016-12-06 15:08:29 +02:00
page.rb	move parfait into register	2015-11-18 12:04:25 +02:00
README.md	move parfait into register	2015-11-18 12:04:25 +02:00
space.rb	update gems and fix tests	2016-12-06 12:08:18 +02:00
symbol_adapter.rb	rename object_type to instance_type	2016-02-25 12:16:13 -08:00
type.rb	move soml tests out, small cleanup	2016-12-06 15:08:29 +02:00
value.rb	fix docs for rename	2016-02-25 12:03:11 -08:00
variable.rb	rename variable type to value_type	2016-02-25 11:41:03 -08:00
word.rb	fix docs for rename	2016-02-25 12:03:11 -08:00

README.md

Notice of change

The stuff below, like the whole of Parfait, was written before soml. Ie before there was a seperate language to compile a higher language to. Soml is not so dynamic, could do without much of the ObjectSpace that is the core of Parfait.

So things will change. How will become clear when soml is finished.

Parfait: a thin layer

Parfait is the run-time of the vm. To be more precise, it is that part of the run-time needed to boot soml.

The run-time needs to contain quite a lot of functionality for a dynamic system. And a large part of that functionality must actually be used at compile time too.

We reuse the Parfait code at compile-time, to create the data for the compiled vm. To do this the vm (re) defines the object memory (in parfait_adapter).

To do the actual compiling we parse and compile the parfait code and inline it to appropriate places.

A work in progress that started from here : http://salama.github.io/2014/06/10/more-clarity.html went on here http://salama.github.io/2014/07/05/layers-vs-passes.html

A step back: the code (program) we compile runs at run - time. And so does parfait. So all we have to do is compile it with the program.

And thus parfait can be used at run-time.

It's too simple: just slips off the mind like a fish into water.

Parfait has a brother, the Builtin module. Builtin contains everything that can not be coded in ruby, but we still need (things like List access).

Vm vs language- core

Parfait is not the language core library. Core library functionality differs between languages and so the language core lib must be on top of the vm parfait.

To make this point clear, i have started using different names for the core classes. Hopefully more sensible ones, ie List instead of Array, Dictionary instead of Hash.

Also Parfait is meant to be as thin as humanly possibly, so extra (nice to have) functionality will be in future modules.