Re: [Doxygen-users] @cond without section label

[Alex E. <AE...@ma...>]

Of course, sorry about that. This is in a .c source file:

/// @cond
const mlInt     SINE_INDEX_SCALE     = INT_MAX/SINE_RESOLUTION;    
const mlInt     kScaledTwoPi            = INT_MAX;
const mlInt     kScaledPi               = (kScaledTwoPi >> 1);
const mlInt     kScaledPiOverTwo        = (kScaledPi >> 1);
const mlInt     kScaledThreePiOverTwo   = (3*kScaledPiOverTwo);
const mlInt spec_storage(MEM2)* kLookupCos = NULL;
const mlInt spec_storage(MEM2)* kLookupSin = NULL;
/// @endcond

Doxygen version 1.7.3

With the above code, it doesn't ignore those constants and throws the warnings.

If I change: ///@cond
to:                /// @cond ASDF

Then it ignores it as I'd like it to do.  Any ideas?


-----Original Message-----
From: Dimitri Van Heesch [mailto:do...@gm...] 
Sent: March-02-11 12:21 PM
To: Alex Escott
Cc: dox...@li...
Subject: Re: [Doxygen-users] @cond without section label


On Mar 1, 2011, at 18:09 , Alex Escott wrote:

> Hi all, I'm trying to use the @cond / @endcond tags to ignore a section of code unconditionally... I can only get it to work if I put a section label on it though. From the docs it says "If the section label is omitted, the section will be excluded from processing unconditionally."
>  
> But if I leave it out, the line with the @cond causes output: warning: Found unknown command `\void'
>  
> And the @endcond line gives the output:  "Found \endcond command without matching \cond"
>  
> Am I missing something?

I don't know, but we are missing the example that shows the problem along with other trivia, like the version of doxygen you are using.

Regards,
  Dimitri