On Wed, Dec 4, 2013 at 10:55 AM, <
doxygen-users-requ...@lists.sourceforge.net> wrote:
> Date: Wed, 27 Nov 2013 10:51:40 -0800
> From: mathog <mat...@caltech.edu>
> On 27-Nov-2013 07:42, Ron Wilson wrote:
> > Your enumeration could be expressed as an "enum" type, optionally using
> > one
> > or more "typedef"s to declare variables that use the enumeration.
>
> I was hoping for the one or two line tag to add to the doxygen
> documentation in the include file, rather than the thousand line rewrite
> of both the include files and all the code that uses them.
>
> Since Doxygen must have somewhere a data representation for
>
> U_EMF_LOGBRUSH_lbStyle_Qualifiers <- EMF LB_Style Enumeration
>
> it seemed likely that somewhere in its large set of commands Doxygen
> would have one that
> would result in
>
> U_EMF_LOGBRUSH_lbStyle_Qualifiers <- EMF LB_Style Enumeration
> U_EMF_LOGBRUSH_lbStyle_Qualifiers <- WMF BrushStyle Enumeration
>
Doxygen only sees #define symbols as individual symbols. Doxygen doesn't
infer any semmantic relationship between them even if you group them
together
using Doxtgen mark-up.
Using @defgroup, the closest aproximation I can come up with would be to
define (to Doxygen) a "master group", then each "use group" would @ref
(or @see) the master group and note the valid range and/or other exceptions.
(FYI, you would not need to rewrite your code. An enum is an integral type,
so
enum BrushStyle {
STYLE_SOLID,
};
int CurrentStyle = STYLE_SOLID;
is valid C. (Some compilers will emit warnings, but this is valid.))
------------------------------------------------------------------------------
Sponsored by Intel(R) XDK
Develop, test and display web and hybrid apps with a single code base.
Download it for free now!
http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
_______________________________________________
Doxygen-users mailing list
Doxygen-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/doxygen-users
