remove traces of salama

Gemfile.lock

@@ -106,4 +106,4 @@ DEPENDENCIES
   thor (= 0.19.1)
 
 BUNDLED WITH
-   1.14.6
+   1.15.1

README.md

@@ -1,4 +1,4 @@
-[![Build Status](https://travis-ci.org/ruby-x/rubyx.svg?branch=master)](https://travis-ci.org/ruby-x/salama)
+[![Build Status](https://travis-ci.org/ruby-x/rubyx.svg?branch=master)](https://travis-ci.org/ruby-x/rubyx)
 [![Code Climate](https://codeclimate.com/github/ruby-x/rubyx/badges/gpa.svg)](https://codeclimate.com/github/ruby-x/rubyx)
 [![Test Coverage](https://codeclimate.com/github/ruby-x/rubyx/badges/coverage.svg)](https://codeclimate.com/github/ruby-x/rubyx)
 
@@ -40,7 +40,7 @@ risc layer. That way test runs on the interpreter reveal most issues.
 
 ### Debugger
 
-And after the interpreter was done, i wrote a [visual debugger](https://github.com/ruby-x/salama-debugger).
+And after the interpreter was done, i wrote a [visual debugger](https://github.com/ruby-x/rubyx-debugger).
 It is a simple opal application that nevertheless has proven great help both in figuring out
 what is going on, and in finding bugs.
 
@@ -71,7 +71,7 @@ And generally optimize and work towards that perfect world (we never seem to be
 
 
 
-Contributing to salama
+Contributing to rubyx
 -----------------------
 
 Probably best to talk to me, if it's not a typo or so.

Rakefile

@@ -26,7 +26,7 @@ Rake::RDocTask.new do |rdoc|
   version = File.exist?('VERSION') ? File.read('VERSION') : ""
 
   rdoc.rdoc_dir = 'rdoc'
-  rdoc.title = "salama #{version}"
+  rdoc.title = "rubyx #{version}"
   rdoc.rdoc_files.include('README*')
   rdoc.rdoc_files.include('lib/**/*.rb')
 end

lib/mom/README.rd

@@ -5,7 +5,7 @@ It is meant to make the transition (between vool and risc) easier to understand.
 
 Previous efforts were doing the transition without an intermediate layer. But while
 this was possible, it was more difficult than need be, and so we go to the old saying
-than everything in computing can be fixed by another layer :-)
+that everything in computing can be fixed by another layer :-)
 
 ## Recap
 
@@ -49,7 +49,7 @@ no registers
 
 ### Instruction based
 
-So a machine than language. No control structures, but compare and jump instructions.
+So a machine rather than a language. No control structures, but compare and jump instructions.
 
 No send or call, just objects and jump.
 

lib/risc/README.md

@@ -36,7 +36,7 @@ There is an interpreter that can interpret compiled register machine programs.
 This is very handy for debugging (an nothing else).
 
 Even more handy is the graphical interface for the interpreter, which is in it's own repository:
-salama-debugger.
+rubyx-debugger.
 
 Arm / Elf
 =========

lib/risc/boot.rb

@@ -35,7 +35,7 @@ module Risc
     # And so we have a chicken and egg problem. At the end of the boot function we want to have a
     # working Space object
     # But that has instance variables (List and Dictionary) and off course a class.
-    # Or more precisely in salama, a Type, that points to a class.
+    # Or more precisely in rubyx, a Type, that points to a class.
     # So we need a Type, but that has Type and Class too. hmmm
     #
     # The way out is to build empty shell objects and stuff the neccessary data into them

rubyx.gemspec

@@ -8,7 +8,7 @@ Gem::Specification.new do |s|
   s.email = 'torsten@villataika.fi'
   s.extra_rdoc_files = ['README.md']
   s.files = %w(README.md LICENSE.txt Rakefile) + Dir.glob("lib/**/*")
-  s.homepage = 'https://github.com/ruby-x/salama'
+  s.homepage = 'http://ruby-x.org/'
   s.license = 'MIT'
   s.require_paths = ['lib']
   s.summary = 'RubyX is a native object vm without any c, one day possibly a ruby vm'

stash/soml/fragments/test_hello.rb

@@ -7,12 +7,12 @@ class TestHello < MiniTest::Test
     @string_input = <<HERE
 class Space
   int main()
-    "Hello Raisa, I am salama".putstring()
+    "Hello Raisa, I am rubyx".putstring()
   end
 end
 HERE
     @length = 37
-    @stdout = "Hello Raisa, I am salama"
+    @stdout = "Hello Raisa, I am rubyx"
     check
   end
 end

test/README.md

@@ -7,7 +7,7 @@ But it is difficult to write tests when you don't know what the functionality is
 Also TDD does not really help as it assumes you know what you're doing.
 
 I used minitest as the framework, just because it is lighter and thus when the
-time comes to move to salama, less work.
+time comes to move to rubyx, less work.
 
 ### All
 

test/rubyx/fragments/test_many_itos.rb

@@ -15,7 +15,7 @@ module Rubyx
     str
 HERE
       @length = 37
-      @stdout = "Hello Raisa, I am salama"
+      @stdout = "Hello Raisa, I am rubyx"
       check
     end
   end

test/vm/method_compiler/test_call_expression.rb

@@ -35,7 +35,7 @@ module Risc
     end
 
     def test_call_string_put
-      @input    = s(:call, :putstring,s(:arguments),s(:receiver,s(:string, "Hello Raisa, I am salama")))
+      @input    = s(:call, :putstring,s(:arguments),s(:receiver,s(:string, "Hello Raisa, I am rubyx")))
       check
     end