> Eek. My, my. I may look into beefing that up then, though it looks
> like you've done a fine job already.I've implemented a handful for RDoc::Parser::Ruby, and that's probably
the easiest place to add more.
I'm also slowly getting up to speed with the codebase in the hope of
contributing tests, and improving texinfo generation. Thanks for the
pointer to RDoc::Parser::Ruby as a place to start.
Chris
Not yet, it's only in my head.
On Jul 24, 2008, at 00:55 AM, Marcin Raczkowski wrote:
Eric Hodel wrote:
On Jul 23, 2008, at 12:33 PM, Marcin Raczkowski wrote:
I was thinking about using ParseTree + friends for this project, but having a documentation is a big bonus, if I'll have sudden attack of craziness, i'll try to make Rdoc parser spit out something similar to PareseTree's AST but with links to documentation string.
In a future version, we'll use ruby_parser to extract documentation, which has a UnifiedRuby-compatible output.
Did you start any work towards that goal?
On my Github there's a documentation parser that uses ruby_parser:
http://www.github.com/jeremymcanally/docr
Don't try to run the bin; I was using RDoc's stuff but I switched to
ruby_parser and I'm not sure that I ever hooked it back in properly.
In any event, you can use lib/docr/parser.rb to get documentation out
of files and have it placed in a Hash structure. It'd be a place to
start at least...
--Jeremy
On Thu, Jul 24, 2008 at 3:48 AM, Eric Hodel <drbrain@segment7.net> wrote:
On Jul 24, 2008, at 00:55 AM, Marcin Raczkowski wrote:
Eric Hodel wrote:
On Jul 23, 2008, at 12:33 PM, Marcin Raczkowski wrote:
I was thinking about using ParseTree + friends for this project, but
having a documentation is a big bonus, if I'll have sudden attack of
craziness, i'll try to make Rdoc parser spit out something similar to
PareseTree's AST but with links to documentation string.In a future version, we'll use ruby_parser to extract documentation,
which has a UnifiedRuby-compatible output.Did you start any work towards that goal?
Not yet, it's only in my head.
--
http://jeremymcanally.com/
http://entp.com/
My books:
http://humblelittlerubybook.com/ (FREE!)
Jeremy McAnally wrote:
On my Github there's a documentation parser that uses ruby_parser:
http://www.github.com/jeremymcanally/docrDon't try to run the bin; I was using RDoc's stuff but I switched to
ruby_parser and I'm not sure that I ever hooked it back in properly.
In any event, you can use lib/docr/parser.rb to get documentation out
of files and have it placed in a Hash structure. It'd be a place to
start at least...--Jeremy
Great, so it extracts ruby code with ruby_parser and documentation?
anyway I'll check it out.
Yeah it uses ruby_parser's ability to get at comments to pull them out
and stick in that structure. IIRC the bin should work fine but I
can't really remember very well. If so, it's basically a very very
basic RDoc replacement that uses ruby_parser. 
--Jeremy
On Thu, Jul 24, 2008 at 9:35 AM, Marcin Raczkowski <mailing.mr@gmail.com> wrote:
Jeremy McAnally wrote:
On my Github there's a documentation parser that uses ruby_parser:
http://www.github.com/jeremymcanally/docrDon't try to run the bin; I was using RDoc's stuff but I switched to
ruby_parser and I'm not sure that I ever hooked it back in properly.
In any event, you can use lib/docr/parser.rb to get documentation out
of files and have it placed in a Hash structure. It'd be a place to
start at least...--Jeremy
Great, so it extracts ruby code with ruby_parser and documentation?
anyway I'll check it out.
--
http://jeremymcanally.com/
http://entp.com/
My books:
http://humblelittlerubybook.com/ (FREE!)