f9a89db10c
fix integer offset bug (which only didn’t cause errors as fixnums are still an order too big and the famous +1 error hit the empty space)
73 lines
1.7 KiB
Ruby
73 lines
1.7 KiB
Ruby
#
|
|
#
|
|
# In rubyx everything truely is an object. (most smalltalk/ruby systems use a union
|
|
# for integers/pointers that are called objects, but are really very different)
|
|
#
|
|
# Objects have type as their first member. No exception.
|
|
#
|
|
# So where is the data? In DataObjects. DataObjects are opague carriers of data.
|
|
# Opague to rubyx that is. There is no way to get at it or pass the data around.
|
|
#
|
|
# To use Data, Risc instructions have to be used. Luckily there is not soo much one
|
|
# actually wants to do with data, moving it between DataObject , comparing and
|
|
# logical and math operation that are bundled into the OperatorInstruction.
|
|
#
|
|
# For safe access the access code needs to know the length of the data, which is
|
|
# encoded in the class/type name. Ie An Integer derives from Data4, which is 4 long
|
|
# ( one for the type, one for the next, one word for the integer and currently still a marker)
|
|
#
|
|
# DataObjects still have a type, and so can have objects before the data starts
|
|
#
|
|
# A marker class
|
|
module Parfait
|
|
class DataObject < Object
|
|
def initialize
|
|
super
|
|
end
|
|
def self.integer_index
|
|
type_length
|
|
end
|
|
def data_length
|
|
raise "called #{self}"
|
|
end
|
|
def data_start
|
|
return get_type.get_length
|
|
end
|
|
end
|
|
|
|
class Data4 < DataObject
|
|
def self.memory_size
|
|
4
|
|
end
|
|
def data_length
|
|
4
|
|
end
|
|
def padded_length
|
|
2 * 4
|
|
end
|
|
end
|
|
|
|
class Data8 < DataObject
|
|
def self.memory_size
|
|
8
|
|
end
|
|
def data_length
|
|
8
|
|
end
|
|
def padded_length
|
|
8 * 4
|
|
end
|
|
end
|
|
class Data16 < DataObject
|
|
def self.memory_size
|
|
16
|
|
end
|
|
def data_length
|
|
16
|
|
end
|
|
def padded_length
|
|
16 * 4
|
|
end
|
|
end
|
|
end
|