From: Charles Mills <cmills@...>
Date: 2004-10-06T01:16:45+09:00
Subject: Re: problem with rdoc and extensions

On Oct 4, 2004, at 9:34 PM, Ara.T.Howard@noaa.gov wrote:

> On Tue, 5 Oct 2004, Dave Thomas wrote:
>
>>
>> On Oct 4, 2004, at 18:36, Charles Mills wrote:
>>
>>> Here I am replying to my own post...
>>> I looked at the rdoc C parser, it doesn't look like rdoc maintains 
>>> its
>>> state between each .c file.  Is this what is going on?
>>
>> That's correct - it would be inappropriate to do that when RDoc is 
>> used
>> (for example) to document all the Ruby extensions.
>>
>> I'm not sure of an easy way to handle your particular problem, apart,
>> perhaps from an ugly cheat. In each .c file that defines classes based
>> on the external module, put a definition of the module variable and 
>> the
>> define_module line in an ifdef's out chunk of code (see, I said it was
>> ugly)
>
> how about using cpp, or cat even, to inline all your c sources and the
> rdoc'ing one giant source file?

That is a great idea.  Tried it and it works well.  You obviously don't 
get a list of all the .c files in the project, but that is not really a 
problem (if it become one Daves idea looks like it solves that).

Thanks for the help,
Charlie