After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 733451 - volatile declaration on member functions is not handled as xml attribute
volatile declaration on member functions is not handled as xml attribute
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.8.7-GIT
Other Linux
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2014-07-20 12:28 UTC by m.pricejones
Modified: 2014-08-28 16:17 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description m.pricejones 2014-07-20 12:28:29 UTC
If I have a class with:

  class MyClass
  {
  public:

      /*!
        \return If class is true.
      */
      bool is_true() volatile;

  };

Then the 'volatile' part is not converted to an xml attribute for the resulting 'memberdef' for 'is_true' in the xml output. It does appear in the 'argsstring' property for the 'memberdef'. This might be deliberate but I'm not sure why.

We currently have a work around for it using the argsstring for the Breathe project.

Kind regards,
Michael
Comment 1 m.pricejones 2014-07-20 12:31:55 UTC
My confusion is partly because the 'xsd' for the xml output describe the 'memberdef' has having a 'volatile' DoxBool attribute.
Comment 2 Dimitri van Heesch 2014-08-08 12:34:00 UTC
Confirmed, the attribute should have been present. 
Should be fixed in the next GIT update.
Comment 3 Dimitri van Heesch 2014-08-21 17:15:09 UTC
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.8. Please verify if this is indeed the case. Reopen the
bug if you think it is not fixed and please include any additional information 
that you think can be relevant (preferrably in the form of a self-contained example).
Comment 4 m.pricejones 2014-08-28 16:17:08 UTC
I can confirm that this is fixed from testing a build from the 1.8.8 source bundle.

Thank you for the swift fix and for the whole doxygen project!