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

Const treatment (Origin: bugzilla #707825) #5292

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.5 on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2013-09-10 02:22:35 +0000, Zoltan Kocsi wrote:

Created attachment 254542
The doxyfile

Attached are a very simple C testfile and a doxyfile to process it.
The C file demonstrates two problems.

  1. If a function returns a pointer to a constant object and the object is a structure, then in the documentation the const qualifier is missing from the function's prototype.

  2. Even if the INLINE_INFO flag is set to YES in the doxyfile, the [inline] qualifier is missing from the documentation.

Maybe it is just an incorrect doxyfile, but no matter what I do, I can't these two things to behave as they should.

Doxygen 1.8.4 has the exact same problems.

On 2013-09-10 02:23:40 +0000, Zoltan Kocsi wrote:

Created attachment 254543
The test C file

On 2013-09-10 07:02:56 +0000, Zoltan Kocsi wrote:

Sorry, my fault.

The second problem reported is not valid.
Doxygen properly extracts the "inline" feature, only the way it is shown has changed and I looked for the old style marker.

The first problem, however,

On 2013-09-22 08:23:48 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next GIT update.

On 2013-12-24 18:59:31 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.6. 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).

@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