On Mon, May 18, 2009 at 2:40 PM, Wouter van Ooijen <wouter@voti.nl> wrote:
>> There is nothing that would prevent you from using Doxygen for this. You
>> have to write the assembly calling sequence for each target CPU anyway,
>> and if you write it in the function's header comment, it can be
>> extracted by Doxygen.
>
> OK, but could it generate *both* C and asm calling documentation from
> one source? Currently I write something like
>
> =A0 =A0 =A0 =A0 =A0#interface mkt_pin_direction
> =A0 =A0 =A0 =A0 =A0 =A0 #parameter N unsigned int
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0number of the IO pin
> =A0 =A0 =A0 =A0 =A0 =A0 #parameter D unsigned int
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0direction for the pin
>

Maybe Python/Perl can come to the rescue. I have not used doxygen
myself (never written any big codes myself), but google found this.
http://www.stack.nl/~dimitri/doxygen/faq.html
http://rudy.mif.pg.gda.pl/~bogdro/inne/asm4doxy.txt

Not so sure if that helps...

-- =

Xiaofan http://mcuee.blogspot.com

-- =

http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist