ruby-x/rubyx
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

fix spelling

Browse Source
This commit is contained in:
Torsten Ruger
2014-08-28 22:32:53 +03:00
parent 35b738639b
commit 99b4468599
6 changed files with 32 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
lib/virtual/README.md
View File

@ -5,13 +5,14 @@ This is really an OV (object value) not object oriented machine.
Integers and References are Values. We make them look like objects, sure, but they are not.
Symbols have similar properties and those are:
- eqality means identity
- no chhange over lifetime
- equality means identity
- no change over lifetime
It's like with Atoms: they used to be the smallest possible physical unit. Now we have electrons, proton and neutrons.
And so objects are made up of Values (not objects), integers, floats , references and possibly more.
Values have type in the same way objects have a class. We keep track of the type at runtime.
Values have type in the same way objects have a class. We keep track of the type of a value at runtime, also in an
similar way that objects have their classes at runtime.
### Layers
@ -21,12 +22,15 @@ comile the ast layer into Virtual:: objects
The main objects are BootSpace (lots of objects), BootClass (represents a class),
CompiledMethod (with Blocks and Instruction).
*Virtual* Instructions get further transformed into *register* instructions. This is done by an abstractly defined
**Virtual** Instructions get further transformed into **register** instructions. This is done by an abstractly defined
Register Machine with basic Intructions. A concrete implementation (like Arm) derives and creates derived
Instructions.
The transformation is implemented as **passes** to make it easier to understand what is going on. Also this makes it
easier to add functionality and optimisations from external (to the gem) sources.
The final transformation assigns Positions to all boot objects (Linker) and assembles them into a binary representation.
The data- part is then a representation of classes in the *parfait* runtime. And the instrucions make up the
The data- part is then a representation of classes in the **parfait** runtime. And the instrucions make up the
funtions.
### Accessible Objects
@ -46,9 +50,10 @@ The micro-kernel idea is well stated by: If you can leave it out, do.
As such we are aiming for integer and reference (type) support, and a minimal class system
(object/class/aray/hash/string).
(object/class/aray/hash/string). It is possible to add types to the system in a similar way as we add classes,
and also implement very machine dependent functionality which nevertheless is fully wrapped as OO.
*Parfait* is that part of the runtime that can be coded in ruby. It is parsed, like any other code and always included
in the resulting binary. Builtin is the part of the runtime that can not be coded in ruby (but is still needed). This
is coded y construction CompiledMethods in code and neccesarily machine dependant.
**Parfait** is that part of the runtime that can be coded in ruby. It is parsed, like any other code and always included
in the resulting binary. **Builtin** is the part of the runtime that can not be coded in ruby (but is still needed). This
is coded by construction CompiledMethods in code and neccesarily machine dependant.