Ruby

From eqqon

(Difference between revisions)
Jump to: navigation, search
(→The Future of Ruby)
(changed the position of the articles)
Line 1: Line 1:
 +
__NOTOC__
<div style="float:right;">[[Image:Ruby_logo.gif]]</div>
<div style="float:right;">[[Image:Ruby_logo.gif]]</div>
 +
= The Future of Ruby =
 +
Yukihiro Matsumoto's C implementation of Ruby aka MRI (Version 1.8) is now considered the '''Quasi-Standard of the Ruby Language''' because there has never been an explicit language standard for Ruby. As the number of implementations grows a standard seems to become necessary to prevent the horror szenario of totally incompatible interpreters. [[The Future of Ruby|Read on ...]]
 +
= Extending Ruby in C =  
= Extending Ruby in C =  
-
We found that the README.ext from Ruby's source distribution is not comfortable to read so we decided to mirror it on our site with proper formatting and some helpful additions: <big><big>[[Ruby C Extension|Ruby1.8 extension API]]</big></big>.
+
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. [[Ruby C Extension|Read on ...]].
 +
 
-
----
 
-
=== More Ruby Resources ===
+
----
 +
===external links===
<div style="clear:left;"></div>
<div style="clear:left;"></div>
Line 46: Line 51:
|}
|}
-
 
-
== The Future of Ruby ==
 
-
Yukihiro Matsumoto's C implementation of Ruby aka MRI (Version 1.8) is now considered the '''Quasi-Standard of the Ruby Language''' because there has never been an explicit language standard for Ruby. As the number of implementations grows a standard seems to become necessary to prevent the horror szenario of totally incompatible interpreters. [[The Future of Ruby|Read on ...]]
 
-
 
-
 
-
 
-
__NOTOC__
 

Revision as of 19:03, 7 August 2007

Ruby logo.gif

The Future of Ruby

Yukihiro Matsumoto's C implementation of Ruby aka MRI (Version 1.8) is now considered the Quasi-Standard of the Ruby Language because there has never been an explicit language standard for Ruby. As the number of implementations grows a standard seems to become necessary to prevent the horror szenario of totally incompatible 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

  • JRuby A very complete implementation of the interpreter in Java.
  • YARV The site of the virtual machine which has been merged into 1.9.
  • Ruby.NET Still incomplete and unoptimized .NET compiler for Ruby.
  • Rubinious An implementation based loosely on the Smalltalk-80 VM architecture.
  • Iron Ruby This implementation by Microsoft has been presented but not yet released.

Documentation

GUI Toolkit Bindings

Retrieved from "http://www.eqqon.com/index.php/Ruby"