On Tue, Apr 8, 2014 at 3:21 PM, Robert Dailey wrote:
...
> however I'd like to see easier ways to do this in the future, such as:
>
...
> - "Smart" parsing that determines if there is any "meaningful" content
> in a namespace before parsing it out.
>
Hear! Hear! Though clearly an issue of sem
Thanks Dimitri.
I elected to go with EXCLUDE_SYMBOLS, however I'd like to see easier
ways to do this in the future, such as:
- An @exclude tag, which is effectively the same as @cond .. @endcond
but only for the single entity the documentation block applies to
- "Smart" parsing that determines if
On 08 Apr 2014, at 15:33 , Robert Dailey wrote:
> In my code I have a couple of forward declarations of classes in other
> distant, unrelated namespaces:
>
> namespace foo
> {
>class bar;
> }
>
> These get parsed out by Doxygen (v1.8.6) and appear empty in the HTML
> output. Is there a way
In my code I have a couple of forward declarations of classes in other
distant, unrelated namespaces:
namespace foo
{
class bar;
}
These get parsed out by Doxygen (v1.8.6) and appear empty in the HTML
output. Is there a way that Doxygen can be "smart" enough to ignore a
namespace if there isn
