From: Andrea Dallera <andrea@...>
Date: 2010-04-15T01:32:40+09:00
Subject: Re: OT(?): Adapting rdoc to produce documentation for something other  than ruby or c--advisable?

Hei,

	I know SAS and honestly I don't think that RDoc is suitable for the
task: the syntax has more than one case that you will have to handle
yourself. If you want to get it working you'll have to hack the parser
yourself and I don't think that will be very easy.

HTH!

-- 

Andrea Dallera
http://github.com/bolthar/freightrain
http://usingimho.wordpress.com


On Thu, 2010-04-15 at 01:00 +0900, rpardee@gmail.com wrote:
> Hey All,
> 
> In my day job I'm a sas (www.sas.com) programmer.  I've got a plain
> text file of sas macros (roughly equivalent to ruby's methods) for
> which I would love to have rdoc-style documentation.  Specifically,
> I'd like a list of the macros, the params they take, the explanatory
> comments that precede each one & the expandable code listing when you
> click a method name.
> 
> A brief troll through the RDoc::Markup docs makes me wonder if I
> couldn't learn to drive that sufficiently to get rdoc to do this for
> me.
> 
> Can anybody give me a sense for how badly RDoc & I would have to
> torture one another to get this to work?
> 
> In case it's helpful, sas has c-style comments: '*' starts a comment
> until the first following ';' char.  Macro definitions are preceded by
> the keyword %macro, followed by a name & an optional parenthesized,
> comma-delimited list of paraameters.  All lines up to the first
> following %mend keyword are the body of the macro.
> 
> Many thanks!
> 
> -Roy
> 
>