Quoting meta@xxxxxxxxx, on Mon, Jul 11, 2005 at 09:12:25PM -0500:
> I started work on documenting RSS. However, all of the normal methods
> you'd use to traverse the parsed RSS object hierarchy seem to be
> implemented via reflection. Hence, there's no actual code to stick
> comments around to get Rdoc to document the methods.
Yeah, its an oddity of dynamic code.
I think you could make a kind of skeleton of rss classes, with the
methods and no bodies, and run rdoc over it. Crude, but effective.
> Is there a way to deal with this kind of situation using Rdoc? If not, I
> guess I'll submit what I have so far, as it's better than nothing...
And nothing is pretty close to what there is.
The most annoying thing I find with the RSS encoder is failures seem to
return nil. No exception, no error message, you call a method, get nil
back, and then have to start reading the code, and thats not so easy
because many of the methods don't actually exist in text form, they are
created on the fly.
So, anything you can do to help this situation is much appreciated!
Thanks,
Sam
|
