Re: [Doxygen-users] Two strange things about Doxygen and my code

2015-08-31 Thread Bostjan Mihoric
On Sun, Aug 30, 2015 at 12:54 AM, Christoph Lipka wrote: > Am 26.08.2015 um 15:16 schrieb Bostjan Mihoric: > > On Wed, Aug 26, 2015 at 2:41 PM, Christoph Lipka > wrote: > > Am 26.08.2015 um 11:14 schrieb Bostjan Mihoric: > > On Tue, Aug 25, 2015 at 7:14 PM, Christoph Lipka > wrote: > > Am 25.08.

Re: [Doxygen-users] Two strange things about Doxygen and my code

2015-08-29 Thread Christoph Lipka
Am 26.08.2015 um 15:16 schrieb Bostjan Mihoric: > On Wed, Aug 26, 2015 at 2:41 PM, Christoph Lipka > wrote: >> Am 26.08.2015 um 11:14 schrieb Bostjan Mihoric: >>> On Tue, Aug 25, 2015 at 7:14 PM, Christoph Lipka >>> wrote: Am 25.08.2015 um 18:36 schrieb Bostjan Mihoric: [...]

Re: [Doxygen-users] Two strange things about Doxygen and my code

2015-08-26 Thread woody
I have noticed some inconsistencies in the .rtf function. Sometimes it puts the caller and called graph just after the name, and the code listing after that, and at other times it puts the caller and call graph AFTER the code listing. as in foo() call graph caller graph { gray

Re: [Doxygen-users] Two strange things about Doxygen and my code

2015-08-26 Thread Bostjan Mihoric
On Wed, Aug 26, 2015 at 3:56 PM, Dimitri van Heesch wrote: > Hi Bostjan, > And why does the VOID redefine not work? >>> >>> It appears that Doxygen's strategy for warning about undocumented >>> parameters or return types just doesn't expect anyone to ever typedef >>> any other type as "void",

Re: [Doxygen-users] Two strange things about Doxygen and my code

2015-08-26 Thread Dimitri van Heesch
Hi Bostjan, >>> And why does the VOID redefine not work? >> >> It appears that Doxygen's strategy for warning about undocumented >> parameters or return types just doesn't expect anyone to ever typedef >> any other type as "void", and thus doesn't bother to test whether the >> return type and/or

Re: [Doxygen-users] Two strange things about Doxygen and my code

2015-08-26 Thread Bostjan Mihoric
On Wed, Aug 26, 2015 at 2:41 PM, Christoph Lipka wrote: > Am 26.08.2015 um 11:14 schrieb Bostjan Mihoric: >> On Tue, Aug 25, 2015 at 7:14 PM, Christoph Lipka >> wrote: >>> Am 25.08.2015 um 18:36 schrieb Bostjan Mihoric: >>> [...] >>> >>> /// @file >>> >>> /// My typedef. >>> typedef void VOID; >>

Re: [Doxygen-users] Two strange things about Doxygen and my code

2015-08-26 Thread Christoph Lipka
Am 26.08.2015 um 11:14 schrieb Bostjan Mihoric: > On Tue, Aug 25, 2015 at 7:14 PM, Christoph Lipka > wrote: >> Am 25.08.2015 um 18:36 schrieb Bostjan Mihoric: >> [...] >> >> /// @file >> >> /// My typedef. >> typedef void VOID; >> >> /// My simple function. Details. >> extern VOID Function(VOID);

Re: [Doxygen-users] Two strange things about Doxygen and my code

2015-08-26 Thread Bostjan Mihoric
On Tue, Aug 25, 2015 at 7:14 PM, Christoph Lipka wrote: > Am 25.08.2015 um 18:36 schrieb Bostjan Mihoric: > [...] > > /// @file > > /// My typedef. > typedef void VOID; > > /// My simple function. Details. > extern VOID Function(VOID); > > Note that I have enabled OPTIMIZE_OUTPUT_FOR_C, JAVADOC_AU

Re: [Doxygen-users] Two strange things about Doxygen and my code

2015-08-25 Thread Christoph Lipka
Am 25.08.2015 um 18:36 schrieb Bostjan Mihoric: [...] > /// @file > > /// My typedef. > typedef void VOID; > > /// My simple function. Details. > extern VOID Function(VOID); > > Note that I have enabled OPTIMIZE_OUTPUT_FOR_C, JAVADOC_AUTOBRIEF and > enabled all warnings. > > The first thing is that