From: ahoward <ahoward@...>
Date: 2003-06-20T22:55:20+09:00
Subject: Re: reading ruby source

On Fri, 20 Jun 2003, Mauricio [iso-8859-1] Fern�ndez 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

??


-a
--
  ====================================
  | Ara Howard
  | NOAA Forecast Systems Laboratory
  | Information and Technology Services
  | Data Systems Group
  | R/FST 325 Broadway
  | Boulder, CO 80305-3328
  | Email: ara.t.howard@noaa.gov
  | Phone:  303-497-7238
  | Fax:    303-497-7259
  | ~ > ruby -e 'p(%.\x2d\x29..intern)'
  ====================================