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

went over the various readmes

Browse Source
This commit is contained in:
Torsten Ruger
2015-10-07 11:32:48 +03:00
parent 88fc4c0e47
commit e669489419
7 changed files with 57 additions and 42 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
lib/bosl/compiler/README.md
View File

@@ -67,12 +67,12 @@ Messages contain return addresses (yes, plural) and arguments.
The important thing here is that Messages and Frames are normal objects.
### Distinclty future proof
### Distinctly future proof
Bosl is designed to be used as an implementation language for a higher oo language. Some, or
even many, features may not make sense on their own. But these features, like several return
addresses are important to implement the higher language.
addresses, are important to implement the higher language.
In fact, Bosl main purpose is not even to be written. The main purpose is to have a language to
In fact, Bosl's main purpose is not even to be written. The main purpose is to have a language to
compile ruby to. In the same way that the assembler layer in salama is not designed to be written,
we just need it to create our layers.

4
lib/elf/README.md
View File

@@ -11,9 +11,9 @@ I was close to going the wilson way, ie assmble, load into memory and jump
But it is nice to produce executables. Also easier to test, what with segfaults and such.
Executalbe files are not supported (yet?), but object files work. So the only thing that remains is to
Executable files are not supported (yet?), but object files work. So the only thing that remains is to
call the linker on the produced object file. The resulting file is an executable that actually works!!
Thanks to Mikko for starting this arm/elf project in the first place: https://github.com/cyndis/as
This part definately needs tlc, so anyone who is interested, dig in!
This part definitely needs tlc, so anyone who is interested, dig in!

4
lib/parfait/README.md
View File

@@ -1,7 +1,7 @@
### Parfait: a thin layer
Parfait is the run-time of the **vm**.
To be more precise, it is that part of the run-time that can be expressed in ruby.
To be more precise, it is that part of the run-time needed to boot ruby.
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.
@@ -53,7 +53,7 @@ Parfait is not the language (ie ruby) core library. Core library functionality d
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.
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.

6
lib/register/builtin/README.md
View File

@@ -16,3 +16,9 @@ C uses Assembler in this situation, we use Builtin functions.
Slightly more here : http://salama.github.io/2014/06/10/more-clarity.html (then still called Kernel)
The Builtin module is scattered into several files, but that is just so the file doesn't get too long.
Note: This is about to change slightly with the arrival of Bosl. Bosl is a lower level function,
and as such there is not much that we need that can not be expressed in it. My current thinking
is that i can code anything in bosl and will only need the bosl instruction set.
So this whole Builtin approach may blow over in the next months. It had already become clear that
mostly this was going to be about memory access, which in bosl is part of the language.