The Future of Ruby
From eqqon
(Difference between revisions)
m (→Introduction) |
m (→Main implementations) |
||
| Line 4: | Line 4: | ||
There have been some attempts to summarize the language's features but none is complete neither completely up to date with the current MRI. | There have been some attempts to summarize the language's features but none is complete neither completely up to date with the current MRI. | ||
| - | == | + | == Ruby Implementations == |
| + | Currently there are many different implementations of Ruby1.8 which are more or less complete: | ||
| + | |||
=== Ruby 1.9 === | === Ruby 1.9 === | ||
* [http://www.davidflanagan.com/blog/2007_08.html#000131 List of differences between 1.8 and 1.9 by David Flanagan] | * [http://www.davidflanagan.com/blog/2007_08.html#000131 List of differences between 1.8 and 1.9 by David Flanagan] | ||
Revision as of 09:08, 6 August 2007
Introduction
Yukihiro Matsumoto's C implementation of Ruby aka MRI (as time of this writing the stable version of the MRI is Ruby 1.8) is 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 formal standard seems to become necessary to prevent the horror szenario of multiple incompatible interpreters on different platforms.
There have been some attempts to summarize the language's features but none is complete neither completely up to date with the current MRI.
Ruby Implementations
Currently there are many different implementations of Ruby1.8 which are more or less complete: