New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

volatile declaration on member functions is not handled as xml attribute (Origin: bugzilla #733451) #5521

Closed
doxygen opened this Issue Jul 2, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@doxygen
Owner

doxygen commented Jul 2, 2018

status RESOLVED severity normal in component general for ---
Reported in version 1.8.7-GIT on platform Other
Assigned to: Dimitri van Heesch

On 2014-07-20 12:28:29 +0000, m.pricejones@gmail.com wrote:

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

On 2014-07-20 12:31:55 +0000, m.pricejones@gmail.com wrote:

My confusion is partly because the 'xsd' for the xml output describe the 'memberdef' has having a 'volatile' DoxBool attribute.

On 2014-08-08 12:34:00 +0000, Dimitri van Heesch wrote:

Confirmed, the attribute should have been present.
Should be fixed in the next GIT update.

On 2014-08-21 17:15:09 +0000, Dimitri van Heesch wrote:

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).

On 2014-08-28 16:17:08 +0000, m.pricejones@gmail.com wrote:

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!

@doxygen doxygen closed this Jul 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment