Re: [Doxygen-users] enum value of "NONE" is not understood by Doxygen.
Brought to you by:
dimitri
Menu
▾
▴
Re: [Doxygen-users] enum value of "NONE" is not understood by Doxygen.
|
From: Albert <alb...@gm...> - 2014-03-12 17:03:20
|
Hi Diarmuid,
Maybe you can create a small example with the recent acquired knowledge and
file a bug report.
Albert
On Wed, Mar 12, 2014 at 4:46 PM, Diarmuid Kieran
<Dia...@pd...>wrote:
> Just putting the below exchange onto the mailing list in case someone
> might also have an idea about it.
>
>
>
> *From:* Diarmuid Kieran
> *Sent:* Wednesday, March 12, 2014 4:44 PM
> *To:* 'Albert'
> *Subject:* RE: [Doxygen-users] enum value of "NONE" is not understood by
> Doxygen.
>
>
>
> I've discovered the problem, but not the solution. (Sort of like global
> warming!)
>
> There is another file elsewhere in the code which has an enum with an
> identically named member.
>
> If I rename that enum member in the other file, the present enum member
> has its doxygen doc generated successfully without warning. Otherwise, the
> warning and documentation for code are not generated.
>
> Weird thing is that the other enum is in a different namespace, so I don't
> see why its causing a problem, but it is.
>
>
>
> *From:* Albert [mailto:alb...@gm... <alb...@gm...>]
> *Sent:* Wednesday, March 12, 2014 2:37 PM
> *To:* Diarmuid Kieran
> *Subject:* Re: [Doxygen-users] enum value of "NONE" is not understood by
> Doxygen.
>
>
>
> Hi Diarmund
>
> Looks indeed like a local problem. You probably won't be able to send me
> the offending code (proprietary code) so best way would be to remove files
> in batches / directories and see when you get a minimal set or just take
> the files where NONE is defined and run them.
>
> Albert
>
>
>
> On Wed, Mar 12, 2014 at 2:30 PM, Diarmuid Kieran <Dia...@pd...>
> wrote:
>
> I ran the same example as you using the doxyfile you sent and I get the
> same result as you.
>
> And then I ran it using my own doxygen file and - also the same result as
> you! (I had not run the example correctly when I posted on nabble, I now
> realize...)
>
> I also see various places in our code "NONE" as a member of an ENUM
> without problem. It is only causing a problem in one place. Unfortunately,
> I can't figure out why it causes the problem there.
>
>
>
> *From:* Albert [mailto:alb...@gm...]
> *Sent:* Wednesday, March 12, 2014 1:46 PM
>
>
> *To:* Diarmuid Kieran
> *Cc:* dox...@li...
> *Subject:* Re: [Doxygen-users] enum value of "NONE" is not understood by
> Doxygen.
>
>
>
> As requested
>
>
>
> On Wed, Mar 12, 2014 at 1:42 PM, Diarmuid Kieran <Dia...@pd...>
> wrote:
>
> Can you send me the files you are using to test it, I'll run them on my
> side and see if that helps.
>
>
>
> *From:* Albert [mailto:alb...@gm...]
> *Sent:* Wednesday, March 12, 2014 1:39 PM
>
>
> *To:* Diarmuid Kieran
> *Cc:* dox...@li...
> *Subject:* Re: [Doxygen-users] enum value of "NONE" is not understood by
> Doxygen.
>
>
>
> Hi Diarmuid,
>
> I tried it with 1.8.4 and see no warning message and I see on the page of
> the g file the enum completely described.
>
> As I cannot reproduce the problem I'm not sure which setting might cause
> the problem.
>
> Albert
>
>
>
>
>
> On Wed, Mar 12, 2014 at 1:34 PM, Diarmuid Kieran <Dia...@pd...>
> wrote:
>
> Hi Albert,
>
> Thanks for your reply.
>
> I'm using version 1.8.4
>
> I'm not sure what special settings you mean? The config file has been
> changed from the standard alright, but in a lot of places. Is there some
> specific properties you are referring to?
>
> Diarmuid
>
>
>
> *From:* Albert [mailto:alb...@gm...]
> *Sent:* Wednesday, March 12, 2014 12:13 PM
> *To:* Diarmuid Kieran
> *Cc:* dox...@li...
> *Subject:* Re: [Doxygen-users] enum value of "NONE" is not understood by
> Doxygen.
>
>
>
> I tried the example with version 1.8.6 and didn't see a problem / warning
> (standard doxygen configuration file, adding \file command to Aclass.{h,cpp}
> - Which version are you using?
>
> - Any special settings in your doxygen configuration file?
>
> Albert
>
>
>
> On Wed, Mar 12, 2014 at 11:34 AM, didje <dia...@pd...> wrote:
>
> In this example:
>
> AClass.h
>
> enum AnEnum {
> NONE=0, A_VALUE, B_VALUE
> };
>
>
> AClass.cpp
>
> /*! \enum AnEnum
> * \brief Various useful values
> */
>
> /*! \var A_VALUE
> * \brief THe value of A
> */
>
> /*! \var B_VALUE
> * \brief THe value of B
> */
>
> /*! \var NONE
> * \brief A value of zero
> */
>
>
> Doxygen gives me the warning message:
>
> Warning: no matching class member found for AnEnum::NONE
>
> If I change the name of "NONE" to "NONE*X*", I don't have this warning. So
> it would seem that
> "NONE" is not understood properly by doxygen as an enum value.
>
> Does anyone know if I can get around this somehow (other than by renaming
> "NONE"). This would seem to be a bug in Doxygen.
>
>
>
>
> --
> View this message in context:
> http://doxygen.10944.n7.nabble.com/enum-value-of-NONE-is-not-understood-by-Doxygen-tp6541.html
> Sent from the Doxygen - Users mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and their
> applications. Written by three acclaimed leaders in the field,
> this first edition is now available. Download your free book today!
> http://p.sf.net/sfu/13534_NeoTech
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users
>
>
>
> --------------------------------------------------------------------------------
> This e-mail, including any attached files, may contain confidential and
> privileged information for the sole use of the intended recipient. Any
> review, use, distribution, or disclosure by others is strictly prohibited.
> If you are not the intended recipient (or authorized to receive information
> for the intended recipient), please contact the sender by reply e-mail and
> delete all copies of this message.
>
>
>
> --------------------------------------------------------------------------------
> This e-mail, including any attached files, may contain confidential and
> privileged information for the sole use of the intended recipient. Any
> review, use, distribution, or disclosure by others is strictly prohibited.
> If you are not the intended recipient (or authorized to receive information
> for the intended recipient), please contact the sender by reply e-mail and
> delete all copies of this message.
>
>
>
> --------------------------------------------------------------------------------
> This e-mail, including any attached files, may contain confidential and
> privileged information for the sole use of the intended recipient. Any
> review, use, distribution, or disclosure by others is strictly prohibited.
> If you are not the intended recipient (or authorized to receive information
> for the intended recipient), please contact the sender by reply e-mail and
> delete all copies of this message.
>
>
> --------------------------------------------------------------------------------
> This e-mail, including any attached files, may contain confidential and
> privileged information for the sole use of the intended recipient. Any
> review, use, distribution, or disclosure by others is strictly prohibited.
> If you are not the intended recipient (or authorized to receive information
> for the intended recipient), please contact the sender by reply e-mail and
> delete all copies of this message.
>
|
