So how do I go about getting this changed for the Ruby Curses Library?
Sam Overdorf
Personally, in the recent curses program I wrote, I used ruby-ncurses.
It has the disadvantage of not being in the standard library. On the
other hand, it follows the C API very closely. Although documentation
is lacking, the C man pages and the couple of example in the
distribution are really all you need as the translation from the C api
to Ruby is straight-forward and consistent.
Don’t take me wrong, more documentation and a separate more Ruby-esque
API would be nice. It is just that given the almost 1-to-1 mapping
between the two APIs, it was fairly easy to use the C documentation.
I feel that incorporating ruby-ncurses to the standard library would be
better than modifying Curses.
My 2 cents,
Guillaume.
Le 9 oct. 06, à 21:10, Overdorf, Sam a écrit :
On 2006.10.10 10:10, Overdorf, Sam wrote:
So how do I go about getting this changed for the Ruby Curses Library?
Sam Overdorf
The first step in doing that is NOT top-posting 
Write a patch and submit it through rubyforge.org. Remember, though,
that there may be countless programs that depend on the current names.
Personally, I would just use the library as-is since there is no
functional change you would be making.