Re: [BUG] constants parsing
Eric Hodel <[email protected]>
| Newsgroups | gmane.comp.lang.ruby.documentation |
|---|---|
| Message-ID | <[email protected]> |
On Aug 8, 2006, at 5:48 PM, Austin Ziegler wrote:
> Speaking of constant parsing, is it possible to give rdoc a value to
> use instead of the literal value? As an example, in PDF::Writer I
> document the PAGE_SIZES constant reasonably well and I don't need the
> value displayed; it would be good if I could prevent that because it
> ends up making the resulting HTML look pretty bad because the value is
> pretty large.
I don't know, I think the parser is to stupid to get the constant
looking good, and I don't know of a directive to suppress them.
> I know that I could do a workaround (PAGE_SIZES = {} ;
> PAGE_SIZES.replace({ ... })) but that feels as bad as the workaround
> that I'm having to do because I can't tell rdoc that "def foo=(x)" is
> actually supposed to be an attribute. (attr_accessor :foo;
> remove_method :foo=; def foo=(x); ...; end).
Let me say that adding features to RDoc is pretty hard. I still need
lots of time to figure this stuff out. Help would be greatly
appreciated.
--
Eric Hodel - [email protected] - http://blog.segment7.net
This implementation is HODEL-HASH-9600 compliant
http://trackmap.robotcoop.com