rubyx/lib/parfait.rb

# Parfait is the ruby runtime
module Parfait
  TYPE_INDEX = 0
end

require_relative "parfait/object"
require_relative "parfait/data_object"
require_relative "parfait/integer"
require_relative "parfait/factory"
require_relative "parfait/behaviour"
require_relative "parfait/class"
require_relative "parfait/singleton_class"
require_relative "parfait/list"
require_relative "parfait/word"
require_relative "parfait/binary_code"
require_relative "parfait/callable"
require_relative "parfait/block"
require_relative "parfait/callable_method"
require_relative "parfait/sol_method"
require_relative "parfait/dictionary"
require_relative "parfait/type"
require_relative "parfait/cache_entry"
require_relative "parfait/message"
require_relative "parfait/space"
some docs 2016-12-06 10:38:09 +01:00			`# Parfait is the ruby runtime`
			`module Parfait`
start writing parfait witout the module Parfait classes must be unscoped. Now we start parsing Parfait, it must be without the module. Luckily module_eval makes this a breeze. Also remove string interpolation that is not yet processed 2019-02-10 20:00:25 +01:00			`TYPE_INDEX = 0`
some docs 2016-12-06 10:38:09 +01:00			`end`

remove parfait module magic since we are now ruby sorcerers, not just wizards, we remove the Parfait module in the compiler (Still have to avoid the name clashes) 2019-09-09 10:54:45 +02:00			`require_relative "parfait/object"`
			`require_relative "parfait/data_object"`
			`require_relative "parfait/integer"`
			`require_relative "parfait/factory"`
move parfait into register register layer uses parfait models to generate object space so parfait should be part of register (not above it) 2015-11-18 11:04:25 +01:00			`require_relative "parfait/behaviour"`
			`require_relative "parfait/class"`
rename meta to singleton class seems more appropriate, as it is the class for a single object Also seems to be called that on the net (don't remember where the meta came from, but it's gone) 2019-09-23 19:57:33 +02:00			`require_relative "parfait/singleton_class"`
move parfait into register register layer uses parfait models to generate object space so parfait should be part of register (not above it) 2015-11-18 11:04:25 +01:00			`require_relative "parfait/list"`
			`require_relative "parfait/word"`
			`require_relative "parfait/binary_code"`
rename typed_method to callable_method seems to make the essence clearer also extracted base class 2018-07-07 08:11:09 +02:00			`require_relative "parfait/callable"`
add parfait block 2018-07-07 14:50:43 +02:00			`require_relative "parfait/block"`
rename typed_method to callable_method seems to make the essence clearer also extracted base class 2018-07-07 08:11:09 +02:00			`require_relative "parfait/callable_method"`
Rename Vool to Sol Simple is really the descriptive name for the layer Sure, it is "virtual" but that is not as important as the fact that it is simple (or simplified) Also objct (based really) is better, since orientated implies it is a little like that, but only orientated, not really it. Sol only has objects, nothing else Just cause i was renaming anyway 2019-10-03 23:36:49 +02:00			`require_relative "parfait/sol_method"`
move parfait into register register layer uses parfait models to generate object space so parfait should be part of register (not above it) 2015-11-18 11:04:25 +01:00			`require_relative "parfait/dictionary"`
rename layout to type this one goes to caleb for pointing it out. Much better word 2016-02-25 20:50:10 +01:00			`require_relative "parfait/type"`
adding cache entry to parfait 2018-03-17 14:33:39 +01:00			`require_relative "parfait/cache_entry"`
move parfait into register register layer uses parfait models to generate object space so parfait should be part of register (not above it) 2015-11-18 11:04:25 +01:00			`require_relative "parfait/message"`
			`require_relative "parfait/space"`