From: Alexander Bokovoy <a.bokovoy@...>
Date: 2001-12-17T23:29:54+09:00
Subject: [ruby-talk:28769] Re: RDoc - Document Ruby source files

On Mon, Dec 17, 2001 at 11:19:11PM +0900, Dave Thomas wrote:
> Alexander Bokovoy <a.bokovoy@sam-solutions.net> writes:
> 
> > Is there a way to execute some code inside your application in an isolated
> > environment and reliably catch all errors/context without crashing own
> > application in case when some unresolved symbols or something like that
> > are exist?
> 
> Yes, but... is there any way to supply that code with the data it
> needs to run? And are you sure you want me to execute the
> "initiate_self_destruct" method?
Of course, not :)

 
> Perhaps an alternative is to provide a way to document virtual
> classes: classes that only appear at runtime.
This is slightly different from what I have: these classes are not appear
only at runtime. Instead, their stubs are generated at run-time and then
modules that extend them are loaded. These modules are well parsed by rdoc
and reference for them is generated but generated documentation lacks at
least several levels of inheritance -- in my case they were something like
Midgard<NewClass> < MidgardObject < Hash < Object so that rdoc sees only
Midgard<NewClass> < Object.

If I were able to specify which part of code rdoc needs to load and
execute in order to get my stubs that would be good compromise because
then I'd put aforementioned code inside and be happy with documentation
for that classes.

What do you think?

-- 
/ Alexander Bokovoy
$ cat /proc/identity >~/.signature
  `Senior software developer and analyst for SaM-Solutions Ltd.`
---
Nov 21 20:58:58 alconost kernel: VFS: Busy inodes after unmount. 
		    Self-destruct in 5 seconds.  Have a nice day...