rubyx/lib/parfait
Torsten Ruger dd2c2cb975 fix init jump bug
the label for the jump was not translated correctly
call needs to go through to_cpu to create single instance
on the way init order slightly changed
2018-05-01 19:19:04 +03:00
..
behaviour.rb remove Kernel class for clarification 2018-04-02 17:06:31 +03:00
binary_code.rb auto extend binary code 2018-04-03 15:07:36 +03:00
cache_entry.rb adds a lot of to_ssss 2018-04-17 20:26:15 +03:00
class.rb moving vool_method to parfait 2017-12-10 20:47:26 +02:00
data_object.rb fix integer and data object get/set word 2018-04-01 11:56:04 +03:00
dictionary.rb move parfait up one, as per its module structure 2017-01-18 20:09:43 +02:00
integer.rb fix integer and data object get/set word 2018-04-01 11:56:04 +03:00
list.rb move parfait up one, as per its module structure 2017-01-18 20:09:43 +02:00
message.rb mostly brackets and formatting 2018-03-23 18:55:23 +02:00
named_list.rb move parfait up one, as per its module structure 2017-01-18 20:09:43 +02:00
object.rb continue to rewrite message_setup 2018-04-05 20:37:03 +03:00
page.rb move parfait up one, as per its module structure 2017-01-18 20:09:43 +02:00
README.md polish docs 2018-03-11 16:11:15 +05:30
space.rb remove Kernel class for clarification 2018-04-02 17:06:31 +03:00
symbol_adapter.rb move parfait up one, as per its module structure 2017-01-18 20:09:43 +02:00
type.rb add object method missing as sys exit 2018-04-02 16:49:30 +03:00
typed_method.rb fix init jump bug 2018-05-01 19:19:04 +03:00
vool_method.rb small cleanup 2018-04-02 18:30:03 +03:00
word.rb add data objects 2018-03-25 18:22:02 +03:00

Parfait: a thin layer

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

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 code. To do this the compiler (re) defines the object memory (in parfait_adapter).

A work in progress that started from here : http://ruby-x.org/2014/06/10/more-clarity.html went on here http://ruby-x.org/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 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.