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 763720 - Exclusion of a new line at the end of source code file causing nesting of HTML code for function documentation
Exclusion of a new line at the end of source code file causing nesting of HTM...
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.8.11
Other Mac OS
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2016-03-15 21:55 UTC by wade7368
Modified: 2016-09-05 13:46 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Contains example source files, doxygen template, and screenshots of output. (353.02 KB, application/zip)
2016-03-15 21:55 UTC, wade7368 		Details

Description wade7368 2016-03-15 21:55:16 UTC 
Created attachment 324050 [details]
Contains example source files, doxygen template, and screenshots of output.

When I have a header and source code file such as example.h and example.c and I don't leave a new line at the end of example.c, the HTML documentation for example.h and example.c nests every function after the first into the first function div. See the attached files for example code and screenshots.
Comment 1 albert 2016-03-17 19:04:28 UTC 
Problem is hard to spot in the images but for the function sum_array the box around the code does not end after the code but continues when there is no newline at the end of the function.

I've just pushed a proposed patch to github (pull request 459)
Comment 2 albert 2016-03-19 12:58:55 UTC 
Code has been integrated in doxygen master branch on github
Comment 3 Dimitri van Heesch 2016-09-05 13:46:39 UTC 
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.12. 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).