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 638864 - Cross inclusion of documented headers causes problems.
Cross inclusion of documented headers causes problems.
Status: RESOLVED DUPLICATE of bug 639716
Product: doxygen
Classification: Other
Component: documentation
1.7.3
Other Windows
: Normal major
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2011-01-06 20:43 UTC by alfonse215
Modified: 2011-03-27 12:43 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Two source files that demonstrate the problem. (555 bytes, application/zip)
2011-01-06 20:44 UTC, alfonse215 		Details
Comprehensive test case. (165.66 KB, application/zip)
2011-01-07 06:27 UTC, alfonse215 		Details

Description alfonse215 2011-01-06 20:43:46 UTC 
If you have one header that includes another, and both use the same documented namespace, the first documented entry in the one doing the including doesn't come out correctly. See example.

This did not happen in 1.7.2.
Comment 1 alfonse215 2011-01-06 20:44:28 UTC 
Created attachment 177701 [details]
Two source files that demonstrate the problem.
Comment 2 Dimitri van Heesch 2011-01-06 22:53:56 UTC 
With a default configuration file I see no difference in the output between 1.7.2 and 1.7.3.

Can you please attach a complete example that includes a config file and the generated output?
Comment 3 alfonse215 2011-01-07 06:27:57 UTC 
Created attachment 177717 [details]
Comprehensive test case.

A more comprehensive test case. The fail directory shows what happens when it doesn't work, and the success shows when it does. The only source code or config file difference is the #include statement in the fail case.
Comment 4 alfonse215 2011-02-09 08:01:44 UTC 
Did the test case help?
Comment 5 Dimitri van Heesch 2011-03-27 12:43:39 UTC 
I believe this is another instance of bug 639716, which should be fixed in the next release.

*** This bug has been marked as a duplicate of bug 639716 ***