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 707825 - Const treatment
Const treatment
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.8.5
Other Linux
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2013-09-10 02:22 UTC by Zoltan Kocsi
Modified: 2013-12-24 18:59 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
The doxyfile (78.72 KB, application/octet-stream)
2013-09-10 02:22 UTC, Zoltan Kocsi 		Details
The test C file (1.07 KB, application/octet-stream)
2013-09-10 02:23 UTC, Zoltan Kocsi 		Details

Description Zoltan Kocsi 2013-09-10 02:22:35 UTC 
Created attachment 254542 [details]
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.
Comment 1 Zoltan Kocsi 2013-09-10 02:23:40 UTC 
Created attachment 254543 [details]
The test C file
Comment 2 Zoltan Kocsi 2013-09-10 07:02:56 UTC 
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,
Comment 3 Dimitri van Heesch 2013-09-22 08:23:48 UTC 
Confirmed. Should be fixed in the next GIT update.
Comment 4 Dimitri van Heesch 2013-12-24 18:59:31 UTC 
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).