From: Rich Kilmer <rich@...>
Date: 2001-12-18T02:03:18+09:00
Subject: [ruby-talk:28802] Re: RDoc - Document Ruby source files

All,

One way to approach this would be to list all of the files within the
require path ($:) and let the person incrementally build up the ObjectSpace
by selecting files.  This is all I can think of because Ruby is SO dynamic
that something you write (Alexander) could be changed at runtime by the
loading of another file written by someone else.  Also, native Ruby
extensions dynamically add modules, classes and methods as well (which are
outside the scope of static documenation generation as well).

I think that capturing the documentation of 'static' (.rb) modules, classes
and methods is about the best we can do without the above mentioned
approach.

-Rich



> -----Original Message-----
> From: dave@thomases.com [mailto:dave@thomases.com]On Behalf Of Dave
> Thomas
> Sent: Monday, December 17, 2001 11:45 AM
> To: ruby-talk ML
> Subject: [ruby-talk:28794] Re: RDoc - Document Ruby source files
>
>
> Alexander Bokovoy <a.bokovoy@sam-solutions.net> writes:
>
> > Look at http://www.ruby-lang.org/en/raa-list.rhtml?name=Path
> > RDoc fails to build full documentation for it. It is very
> similar to what
> > I have in my case.
>
> Absolutely. I just don't see what I can do about it. Could you perhaps
> show me some sample code illustrating how I can determine what to run,
> and how I can associate comments with these dynamically generated
> methods?
>
>
> Thanks
>
>
> Dave
>