On Tuesday, November 30, 2004, 3:24:55 AM, Dave wrote:

>> It would be nice to find a solution to this.  First thing that comes
>> to mind: a project that makes the latest RDoc code available as a gem,
>> which installs under a different name than "rdoc", so it doesn't
>> clash.

> It'd be great if someone had the time to do this.

> But then again, you could argue that the same should apply to the 
> interpreter itself---someone finds a bug, then they should be able to
> get a fixed version of the interpreter without having to download from
> the CVS and build...  So perhaps this gem should be a complete Ruby 
> system (interpreter and libraries).

Well, RDoc is the only component that truly feels this need, IMO.
Such a heavyweight gem, being the hack that it is, would be a bit
unwieldy.

But then there's the question of interactions between RDoc versions
and Ruby versions.

I think the best solution would be to have a webapp that accepts code
bundles (tgz or whatever) and RDocs them, showing the user the
results, then throwing away the code afterwards.  This would run with
the more-or-less latest Ruby and RDoc, so you can see what it looks
like.

Any enterprising webapp programmers?  Or any better ideas?

Gavin