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

cleanup

Browse Source
This commit is contained in:
Torsten Ruger
2014-08-18 13:01:52 +03:00
parent 9f292ba618
commit 99e0c0db18
4 changed files with 64 additions and 50 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
lib/sof/README.md
View File

@@ -1,28 +1,30 @@
### Reading the code
Knowing what's going on while coding salama is not so easy: Hnce the need to look at code dumps
Knowing what's going on while coding salama is not so easy: Hence the need to look at code dumps
Hence the need for a code/object file format (remeber an oo program is just objects, some data, some code, all objects)
Hence the need for a code/object file format (remember an oo program is just objects, some data, some code, all objects)
I started with yaml, which is nice in that it has a solid implementation, reads and writes, handles arbitrary objects,
handles graphs and is a sort of readable text format.
I started with yaml, which is nice in that it has a solid implementation, reads and writes, handles arbitrary objects, handles graphs and is a sort of readable text format.
But the sort of started to get to me, because 1) it's way to verbose and 2) does not allow for (easy) ordering.
But the sort of started to get to me, because
1) it's way to verbose (long files, object groups over many pages) and
2) does not allow for (easy) ordering.
Also it was placing references in weird (first seen) places.
To fix this i started on Sof, with an eye to expand it.
The main starting goal was quite like yaml, but with
- more text per line, specifically objects with simle attributes to have a constructor like syntax
- more text per line, specifically objects with simple attributes to have a constructor like syntax
- also short versions of arrays and hashes
- Shorter class names (no ruby/object or even ruby/struct stuff)
- references at the most shallow level
- a possibility to order attributes and specify attributes that should not be serialized
### Salama Object File
Ok, so we all heard about object files, it's the things compilers create so we don't have to have huge compiles and
can link them later.
Ok, so we all heard about object files, it's the things compilers create so we don't have to have
huge compiles and can link them later.
Much fewer know what they include, and that is not because they are not very useful, but rather very complicated.
@@ -32,8 +34,9 @@ An object machine must off course have it's own object files, because:
- we would be forced to read the source every time (slow)
- we would have no language independant format
And i was going to get there, juust not now. I mean i think it's a great idea to have many languages compile and run
on the same object machine. Not neccessarily my idea, but i haven't seen it pulled off. Not that i will.
And i was going to get there, juust not now. I mean i think it's a great idea to have many languages
compile and run on the same object machine.
Not neccessarily my idea, but i haven't seen it pulled off. Not that i will.
I just want to be able to read my compiled code!!