- 
+
@@ -36,7 +36,7 @@
Home
- Kide
+ Salama
Virtual Pi
diff --git a/_posts/2014-04-22-to-see-or-not-to_c.md b/_posts/2014-04-22-to-see-or-not-to_c.md
index c4b039f..82d30a8 100644
--- a/_posts/2014-04-22-to-see-or-not-to_c.md
+++ b/_posts/2014-04-22-to-see-or-not-to_c.md
@@ -31,7 +31,7 @@ ruby core/std-lib
Off course the ruby-core and std libs were designed to do for ruby what libc does for c. Unfortunately they are badly designed and suffer from above brainwash (designed around c calls)
-Since kide is pure ruby there is a fair amount of functionality that would be nicer to provide straight in ruby. As gems off course, for everybody to see and fix.
+Since salama is pure ruby there is a fair amount of functionality that would be nicer to provide straight in ruby. As gems off course, for everybody to see and fix.
For example, even if there were to be a printf (which i dislike) , it would be easy to code in ruby.
What is needed is the underlying write to stdout.
@@ -39,7 +39,7 @@ What is needed is the underlying write to stdout.
Solution
--------
-To get kide up and running, ie to have a "ruby" executable, there are really very few kernel calls needed. File open, read and stdout write, brk.
+To get salama up and running, ie to have a "ruby" executable, there are really very few kernel calls needed. File open, read and stdout write, brk.
So the way this will go is to write syscalls where needed.
diff --git a/_posts/2014-05-20-first-fibo.md b/_posts/2014-05-20-first-fibo.md
index 904f695..ca8a9fd 100644
--- a/_posts/2014-05-20-first-fibo.md
+++ b/_posts/2014-05-20-first-fibo.md
@@ -25,5 +25,5 @@ assmbler i found a fibonachi in 10 or so instructions.
To summarise, function definition and calling (including recursion) works.
If and and while structures work and also some operators and now it's easy to add more.
-So we have a Fibonacchi in ruby using a while implementation that can be executed by kide and outputs the
+So we have a Fibonacchi in ruby using a while implementation that can be executed by salama and outputs the
correct result. After a total of 7 weeks this is much more than expected!
diff --git a/_posts/2014-06-10-more-clarity.md b/_posts/2014-06-10-more-clarity.md
index 17272ba..5bf3f9c 100644
--- a/_posts/2014-06-10-more-clarity.md
+++ b/_posts/2014-06-10-more-clarity.md
@@ -24,7 +24,7 @@ And what are these funtions? get_instance_variable or set too. Same for function
This functionality, ie getting the n'th data in an object, is essential, but c makes such a good point of of it having no place in a public api. So it needs to be implemented in a "private" part and used in a save manner. More on the layers emerging below.
-The Kernel is a module in kide that defines functions which return function objects. So the code is generated, instead of parsed. An essential destinction.
+The Kernel is a module in salama that defines functions which return function objects. So the code is generated, instead of parsed. An essential destinction.
#### System
@@ -50,7 +50,7 @@ Some few machine functions return Blocks, or append their instructions to blocks
The Kernel functions return function objects. Kernel functions have the same name as the function they implement, so Kernel::putstring defines a function called putstring. Function objects (Vm::Function) carry entry/exit/body code, receiver/return/argurmt types and a little more.
-The important thing is that these functions are callable from ruby code. Thus they form the glue from the next layer up, which is coded in ruby, to the machine layer. In a way the Kernel "exports" the machine functionality to kide.
+The important thing is that these functions are callable from ruby code. Thus they form the glue from the next layer up, which is coded in ruby, to the machine layer. In a way the Kernel "exports" the machine functionality to salama.
##### Parfait
@@ -60,22 +60,22 @@ Parfait is heavy on Object/Class/Metaclass functionality, object instance and me
Stdlib would be the next layer up, implementing the whole of ruby functionality in terms of what Parfait provides.
-The important thing here is that Parfait is written completely in ruby. Meaning it get's parsed by kide like any other code, and then transformed into executable form and written.
+The important thing here is that Parfait is written completely in ruby. Meaning it get's parsed by salama like any other code, and then transformed into executable form and written.
-Any executable that kide generates will have Parfait in it. But only the final version of kide as a ruby vm, will have the whole stdlib and parser along.
+Any executable that salama generates will have Parfait in it. But only the final version of salama as a ruby vm, will have the whole stdlib and parser along.
-#### Kide
+#### Salama
-Kide uses the Kernel and Machine layers straight when creating code. Off course.
-The closest equivalent to kide would be a compiler and so it is it's job to create code (machine layer objects).
+Salama uses the Kernel and Machine layers straight when creating code. Off course.
+The closest equivalent to salama would be a compiler and so it is it's job to create code (machine layer objects).
But it is my intention to keep that as small as possible. And the good news is it's all ruby :-)
##### Extensions
-I just want to mention the idea of extensions that is a logical step for a minimal system. Off course they would be gems, but the integesting thing is they (like kide) could:
+I just want to mention the idea of extensions that is a logical step for a minimal system. Off course they would be gems, but the integesting thing is they (like salama) could:
-- use kides existing kernel/machine abstraction to define new functionality that is not possible in ruby
+- use salamas existing kernel/machine abstraction to define new functionality that is not possible in ruby
- define new machine functionality, adding kernel type api's, to create wholly new, possibly hardware specific functionality
I am thinking graphic accellaration, GPU usage, vector api's, that kind of thing. In fact i aim to implement the whole floating point functionality as an extensions (as it clearly not essential for OO).
diff --git a/about.html b/about.html
index db82c1a..0986143 100644
--- a/about.html
+++ b/about.html
@@ -1,6 +1,6 @@
---
layout: site
-title: Kide, where it started
+title: Salama, where it started
---
diff --git a/future_CNAME b/future_CNAME
index 313cf2a..8cd52af 100644
--- a/future_CNAME
+++ b/future_CNAME
@@ -1 +1 @@
-kide.org
+salama.org
diff --git a/ideas.html b/ideas.html
index 033d01e..c707812 100755
--- a/ideas.html
+++ b/ideas.html
@@ -1,7 +1,7 @@
---
layout: main
title: Ruby in Ruby
-sub-title: Kide hopes make the the mysterious more accessible, shed light in the farthest (ruby) corners, and above all, empower you
+sub-title: Salama hopes make the the mysterious more accessible, shed light in the farthest (ruby) corners, and above all, empower you
---
diff --git a/kide/memory.md b/salama/memory.md
similarity index 99%
rename from kide/memory.md
rename to salama/memory.md
index edaab05..18374f7 100644
--- a/kide/memory.md
+++ b/salama/memory.md
@@ -1,5 +1,5 @@
---
-layout: kide
+layout: salama
title: Memory layout and management
---
diff --git a/kide/optimisations.md b/salama/optimisations.md
similarity index 99%
rename from kide/optimisations.md
rename to salama/optimisations.md
index 145e0d6..b0c5cf0 100644
--- a/kide/optimisations.md
+++ b/salama/optimisations.md
@@ -1,5 +1,5 @@
---
-layout: kide
+layout: salama
title: Optimisation ideas
---
diff --git a/kide/threads.md b/salama/threads.md
similarity index 99%
rename from kide/threads.md
rename to salama/threads.md
index cfd869a..870371d 100644
--- a/kide/threads.md
+++ b/salama/threads.md
@@ -1,5 +1,5 @@
---
-layout: kide
+layout: salama
title: Threads are broken
author: Torsten
---
@@ -69,7 +69,7 @@ In an oo system this can be enforced by strict pass-by-value over thread borders
The itc (inter thread communication) objects are the only ones that need current thread synchronization techniques.
The one mechanism that could cover all needs could be a simple lists.
-### Kide
+### Salama
The original problem of what a program does during a kernel call could be solved by a very small number of kernel threads.
Any kernel call would be listed and "c" threads would pick them up to execute them and return the result.
diff --git a/spiritual.md b/spiritual.md
index fe9b669..2e9574f 100755
--- a/spiritual.md
+++ b/spiritual.md
@@ -54,7 +54,7 @@ I noticed that quite quickly after i started the project, i was diverging radica
is not just from my old ideas, which is nice in itself. A certain freshness and the fact that i am not just going over
old ground. No, it's from any old ideas that i am aware of.
-I just noticed another kide project with similar goals, but sort of more traditional choices. Ie llvm to generate binaries
+I just noticed another salama project with similar goals, but sort of more traditional choices. Ie llvm to generate binaries
and a more static aproach. And that would have been me as a younger version. Now i go the long way because i know i have
all the time i need, and what matters is direction, not speed.
diff --git a/what_is.html b/what_is.html
index 8a3ca16..7f3bb83 100644
--- a/what_is.html
+++ b/what_is.html
@@ -1,6 +1,6 @@
---
layout: site
-title: Kide and Ruby, Ruby and Kide
+title: Salama and Ruby, Ruby and Salama
---
+
@@ -36,7 +36,7 @@
Home
diff --git a/kide/layers.html b/salama/layers.html
similarity index 97%
rename from kide/layers.html
rename to salama/layers.html
index 2a9185c..bcf4e8e 100644
--- a/kide/layers.html
+++ b/salama/layers.html
@@ -1,12 +1,12 @@
---
-layout: kide
-title: Kide, a simple and minimal oo machine
+layout: salama
+title: Salama, a simple and minimal oo machine
---
@@ -24,7 +24,7 @@ title: Kide, a simple and minimal oo machine
those classes are derived from Vm versions.
There is an intel directory which contains an expanded version of wilson, but it has yet to be made to fit into - the architecture. So for now kide produces arm code. + the architecture. So for now salama produces arm code.
-
Kide layers
+Salama layers
Map pretty much to top level directories.
There is an intel directory which contains an expanded version of wilson, but it has yet to be made to fit into - the architecture. So for now kide produces arm code. + the architecture. So for now salama produces arm code.
@@ -13,7 +13,7 @@ title: Kide and Ruby, Ruby and Kide
-
and Kide
+and Salama
Vm
-Kide
--The heart of the kide project is kide, the virtual machine
Kide is written in 100% ruby
-Kide uses an existing ruby to bootstrap itself
-Kide generates native code, and ( with 1+2) creates a native ruby virtual machine.
-Kide does not interpret, it parses and compiles (just making sure that's clear)
-Kide uses a statically typed value based core with rtti and oo syntax to achieve this +
Salama
++The heart of the salama project is salama, the virtual machine
Salama is written in 100% ruby
+Salama uses an existing ruby to bootstrap itself
+Salama generates native code, and ( with 1+2) creates a native ruby virtual machine.
+Salama does not interpret, it parses and compiles (just making sure that's clear)
+Salama uses a statically typed value based core with rtti and oo syntax to achieve this (think c++ with ruby syntax)
Kide considers only that core which can not be suplied though an external gem, this is called +
Salama considers only that core which can not be suplied though an external gem, this is called Parfait. It only provides Array and String and an ability to access the operating system, in 100% ruby.
Full ruby stdlib compliance is not an initial project goal, but may be achieved through external libraries