Ruby
From eqqon
(Difference between revisions)
(→The Future of Ruby) |
|||
Line 50: | Line 50: | ||
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 ...]] | 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__ | __NOTOC__ |
Revision as of 07:40, 6 August 2007
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: Ruby1.8 extension API.
More Ruby Resources
Community
|
Different Implementations
|
Documentation
|
GUI Toolkit Bindings
|
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 ...