Re: [Doxygen-users] Doxygen and C function names with modifiers with arguments

2019-07-23 Thread Ron W
On Tue, Jul 23, 2019 at 11:41 AM Leonardo Pereira Santos < leonardo.pereirasan...@onsemi.com> wrote: > There’s an odd behaviour when expanding the macro. > > > If I use a PREDEFINED as suggested: > > PREDEFINED = chess_storage(x)=chess_storage_##x > > > > I get the documentation as > >

Re: [Doxygen-users] Doxygen and C function names with modifiers with arguments

2019-07-23 Thread Leonardo Pereira Santos
: July-19-19 9:14 PM To: doxygen-users Subject: Re: [Doxygen-users] Doxygen and C function names with modifiers with arguments [External Email]: This email arrived from an external source - Please exercise caution when opening any attachments or clicking on links. On Fri, Jul 19, 2019 at 8:03 AM

Re: [Doxygen-users] Doxygen and C function names with modifiers with arguments

2019-07-19 Thread Ron W
On Fri, Jul 19, 2019 at 8:03 AM wrote: > Date: Thu, 18 Jul 2019 21:09:12 + > From: Leonardo Pereira Santos > Subject: [Doxygen-users] Doxygen and C function names with modifiers with > arguments > > Because the directive has a parameter, Doxygens interprets the directive

[Doxygen-users] Doxygen and C function names with modifiers with arguments

2019-07-18 Thread Leonardo Pereira Santos
I'm documenting some embedded C code and some functions have storage modifiers that are specific to the compiler, like so: int chess_storage(x0) firmware_function(unsigned long int chess_storage(a0) param) Because the directive has a parameter, Doxygens interprets the directive as the functi