Ruby
From eqqon
(→Different Implementations) |
|||
| Line 33: | Line 33: | ||
|------------------------- 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] | ||
| Line 50: | Line 49: | ||
* GTK | * GTK | ||
* Ruby-Qt | * Ruby-Qt | ||
| + | |||
| + | |------------------------- style="vertical-align:top;" | ||
| + | || | ||
| + | === Libraries === | ||
| + | *[http://rake.rubyforge.org/ Rake] | ||
| + | *[http://rspec.rubyforge.org/ RSpec (BDD Framework)] | ||
| + | *[http://www.rubyonrails.org/ Rails] | ||
| + | *[http://www.ruby-doc.org/stdlib/libdoc/uri/rdoc/index.html URI] | ||
| + | *[http://www.ruby-doc.org/stdlib/libdoc/pathname/rdoc/index.html Pathname] | ||
|} | |} | ||
Revision as of 11:54, 31 March 2008
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
|
Libraries |