From: Robbie Carlton <robbie.carlton@...>
Date: 2005-09-21T06:54:28+09:00
Subject: Re: Reading the ruby source

------=_Part_30373_4780456.1127253264776
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

thanks for the road-map. I've just got stuck in. README.EXT is very handy,=
=20
and I hadn't even thought of grep (I'm on a mac, and the unix underbelly is=
=20
still not second nature yet).
also, kudos for the funny book why.

On 9/20/05, why the lucky stiff <ruby-talk@whytheluckystiff.net> wrote:
>=20
> Robbie Carlton wrote:
>=20
> >Hi.
> >I'd like to read the ruby source (that is, the source that when compiled=
,
> >yields the ruby interpreter). I have them, and I've had a look, but I=20
> just
> >get overwhelmed. I've never read a big c program before, and I was=20
> wondering
> >if anyone had any advice on where to start, or if there has been any
> >documentation?
> >
> Try README.EXT which comes with Ruby. It'll give ya a quick gloss over
> everything.
>=20
> From there, I'd look over ruby.h and intern.h, which will give you a
> tour of the major structs and functions.
>=20
> When you start diving into the various source files, note the Init_
> functions at the end of each of them. (string.c has an Init_String,
> marshal.c has Init_marshal, etc.) These functions create the actual
> Ruby modules, classes and methods from their C counterparts.
>=20
> _why
>=20
>

------=_Part_30373_4780456.1127253264776--