From: "Mauricio Fernández" <batsman.geo@...>
Date: 2003-06-20T23:01:07+09:00
Subject: Re: reading ruby source

On Fri, Jun 20, 2003 at 10:55:20PM +0900, ahoward wrote:
> > Ruby Core
> >  * dln.c: wraps dlopen or the equiv. function of your platform, not very
> >    interesting
> >  * gc.c: quite easy to follow, of interest only if you want to know how
> >     the GC works internally, but it's just mark & sweep doing "common
> >     sense" things so you can safely skip it.
> >  * st.c: a hash table implementation used internally by Ruby, quite
> >    straightforward
> >  * eval.c: much harder to read as you have to know the node types to
> >    follow it; several functions are essentially a big switch() statement
> >    for a node
> >  * parse.y: this can help you see what different node types correspond
> >    to by having a look at the grammar.
> >  * regex.c: whatever, don't read it :-)
> 
> this is incredibly useful info - can we (you, i, somebody) create a wiki page
> with the following format:
> 
>   sourcea.c: definition
>   sourcebc: definition
>   ...
> 
> then people can add to it at will and i could soon become a really valuable
> resource.
> 
> perhaps http://www.rubygarden.org/ruby?RubyCore

I prefer RubyInterpreterSourceCode, quite verbose but precise.  And then
make a hierarchy (because everything in one page could be too big) w/
 * /Core
 * /BuiltinClasses
 
I'm adding this to the Wiki unless somebody complains here soon :-)

-- 
 _           _                             
| |__   __ _| |_ ___ _ __ ___   __ _ _ __  
| '_ \ / _` | __/ __| '_ ` _ \ / _` | '_ \ 
| |_) | (_| | |_\__ \ | | | | | (_| | | | |
|_.__/ \__,_|\__|___/_| |_| |_|\__,_|_| |_|
	Running Debian GNU/Linux Sid (unstable)
batsman dot geo at yahoo dot com

<doogie> Thinking is dangerous.  It leads to ideas.
	-- Seen on #Debian