Opinion on Ruby maturity, the missing things

From: Paul E.C. Melis [mailto:paul@floorball.nl]
Sent: Friday, July 26, 2002 1:52 PM
To: ruby-talk@ruby-lang.org
Subject: Re: Opinion on Ruby maturity, the missing things

My point being that, yes Ruby (and Perl) is being used in
some cases as an
embedded language, but that’s not because in those instances
people simply
picked up the documentation and started hacking. There simply
is not enough
information available in the docs for that.

Regards,
Paul

Oh, to be sure, there is probably room for a "Writing Extensions with Ruby"
book. Perl has one now. Anyone care to pitch the idea to a publisher? No,
I don’t think I’m qualified, in case you’re going to point at me. :stuck_out_tongue:

I know that’s a book that I would buy, anyway. :slight_smile:

Regards,

Dan

···

-----Original Message-----

As would I. The PickAxe book comes very close, and there’s some good
info in The Ruby Developer’s Guide, but it would be useful to have
documentation on everything in intern.h, as well as "tips-n-tricks"
and platform-specific information. (What compilers can you use on
Windows?, for example.) As long as I’m wishing, I wish for a “Ruby
Extension API reference guide,” too.

A smaller solution might be something on the order of a HOW-TO made
available on ruby-lang.org. At least it wouldn’t have to be pitched to
a publisher.

···

On Fri, 26 Jul 2002 18:58:27 GMT, “Berger, Daniel” djberge@qwest.com wrote:

Oh, to be sure, there is probably room for a "Writing Extensions with Ruby" book. Perl has one now. Anyone care to pitch the idea to a publisher? No, I don't think I'm qualified, in case you're going to point at me. :-P

I know that’s a book that I would buy, anyway. :slight_smile:

Oh, to be sure, there is probably room for a "Writing Extensions with Ruby"

You don't need such a book : you first write your extension in ruby, then
you translate it in C, et voila :slight_smile:

Guy Decoux