Ruby

From eqqon

(Difference between revisions)
Jump to: navigation, search
m (The Future of Ruby)
m (Different Implementations)
Line 29: Line 29:
* [http://plas2003.fit.qut.edu.au/Ruby.NET/ Ruby.NET] Still incomplete and unoptimized .NET compiler for Ruby.  
* [http://plas2003.fit.qut.edu.au/Ruby.NET/ Ruby.NET] Still incomplete and unoptimized .NET compiler for Ruby.  
* [http://rubini.us/ Rubinious] An implementation based loosely on the Smalltalk-80 VM architecture.
* [http://rubini.us/ Rubinious] An implementation based loosely on the Smalltalk-80 VM architecture.
-
* <b>Iron Ruby</b> This implementation by Microsoft has been presented but not yet released.
+
* [http://ironruby.rubyforge.org Iron Ruby The (yet far from complete) C# implementation by Microsoft designed for .NET interoperability].
|------------------------- style="vertical-align:top;"
|------------------------- style="vertical-align:top;"
||
||
 +
=== Documentation ===
=== Documentation ===
* [http://www.rubyist.net/~slagell/ruby/ Ruby Tutorial]
* [http://www.rubyist.net/~slagell/ruby/ Ruby Tutorial]

Revision as of 14:00, 11 November 2007

Ruby logo.gif

The Future of Ruby

Yukihiro Matsumoto's C implementation of Ruby aka Main Ruby Implementation is considered the Quasi-Standard of the Ruby Language since there has never been an explicit language standard for Ruby. As the number of implementations grows, however, a formal standard seems to become necessary to prevent the horror scenario of various non-conform interpreters. Read on ...

Extending Ruby in C

Extending Ruby with C functions is quiet easy. After you have learned the principles and worked through the ambiguous usage of the API functions you get the power of the Ruby language to your C program. Then it is possible to solve the time critical tasks at the C program and the complex part by Ruby. We created a simple tutorial to get quickly familiar with the Ruby C extension API. Read on ....



external links

Community

Different Implementations

Documentation

GUI Toolkit Bindings