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 629249 - Incorrect "References" and "Referenced by"
Incorrect "References" and "Referenced by"
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.7.1
Other Windows
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2010-09-10 10:07 UTC by Jens Burger
Modified: 2015-12-30 10:19 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Example to reproduce the error (25 lines) (354 bytes, text/plain)
2010-09-10 10:11 UTC, Jens Burger 		Details

Description Jens Burger 2010-09-10 10:07:45 UTC 
For plain C-code that contains type-cast in initializer (see attached example), the variables after this initializer are not "Referenced".

In the attached example all variables are listed, but only for the first 3 variables the reference information is correct. The references for the last three identifiers are missing. The problem is the typecast in the initializer "(Bool)" (line 9), if it is removed, everything works fine.

Although the cast is not needed by C-language, it is required by our MISRA-checker.
Comment 1 Jens Burger 2010-09-10 10:11:24 UTC 
Created attachment 169935 [details]
Example to reproduce the error  (25 lines)

This is the example file to reproduce the error. It is not the original source, but it is very similar to the original structure.
Comment 2 albert 2015-09-30 18:22:41 UTC 
I've just pushed a proposed patch to github (pull request 401).
Comment 3 Dimitri van Heesch 2015-10-04 14:20:34 UTC 
Thanks, I've merged the pull request
Comment 4 Dimitri van Heesch 2015-12-30 10:19:34 UTC 
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.11. 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 (preferably in the form of a self-contained example).