From: Austin Ziegler <halostatue@...>
Date: 2005-05-30T22:43:42+09:00
Subject: Re: RI Conceptional Showstopper Bug.

On 5/28/05, Dave Thomas <dave@pragprog.com> wrote:
> On May 28, 2005, at 12:15 AM, Lothar Scholz wrote:
> > Looked further into it and the situation is more worse then i
> > expected. As RI does absolutely not handle the ruby key feature of
> > open classes. If i write somewere a
> >
> > class File
> > def temp_dir; return "c:/myproject/temp"; end
> > end
> >
> > The whole documentation for File is destroyed.
> >
> I'm surprised if this is the case: rdoc and ri go to some trouble to
> handle this.

On an individual run, rdoc and ri do handle this very well. On
multiple runs, I have experienced the same thing as Lothar. That is,
if I generate the system documentation, and then later run ri on
something that adds a method to File, File's documentation may be
corrupted.

ri works very well for initial deployment, but does not work well for
organic growth and management of documentation -- which is what Lothar
is *really* trying to say here, but apparently lacks the tact.

-austin
-- 
Austin Ziegler * halostatue@gmail.com
               * Alternate: austin@halostatue.ca