> Robert Feldt <feldt / ce.chalmers.se> writes:
> 
>> Maybe something along the lines of:
>> 
>> ruby -r rdoc program.rb indata1 ... indatan
>> 
>> could solve parts of this problem? Not sure if its a major problem
>> though...
> 
> That would give me the reflection information, but I'd lose the parse
> of the source code, so I'd miss out on the attribute and aliasing
> information, along with the comments.
> 
> This is a tricky one.

Have you considered anything similar to Python's "doc strings", which are 
carried around with methods at run time?  I don't know if they are 
applicable, but could be fodder for some ideas, since I like the idea of an 
object's documentation being part of its run time structure.

Jason