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 689713 - wrong display of tcl function source code using INLINE_SOURCES
wrong display of tcl function source code using INLINE_SOURCES
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.8.1.2
Other Linux
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2012-12-05 16:23 UTC by r.zaumseil
Modified: 2013-01-20 13:35 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Source code test file (84 bytes, text/x-tcl)
2012-12-05 16:23 UTC, r.zaumseil 		Details

Description r.zaumseil 2012-12-05 16:23:25 UTC 
Created attachment 230790 [details]
Source code test file

INLINE_SOURCES work correct under 1.8.0 but not under 1.8.2
(probably also not under 1.8.1). Under the later versions the
included function source code is not correctly formatted.
But the code is correctly formatted in the file code display.

There seem to many </div> tags in the generated html file.
Comment 1 r.zaumseil 2013-01-09 20:31:28 UTC 
Same problem under doxygen 1.8.3.

As a test I compiled a version with parameter schowLineNumbers in
function TclLanguageScanner::parseCode() set to TRUE and voila,
everything was OK. It is used as variable tcl.code_linenumbers in
function tcl_codify().

HTH rene
Comment 2 Dimitri van Heesch 2013-01-12 13:00:19 UTC 
The real problem is that every code line should be preceded with

  tcl.code->startCodeLine(tcl.code_linenumbers);

and end with a call to

  tcl.code->endCodeLine();

to produce proper output. 

I'll correct this.
Comment 3 Dimitri van Heesch 2013-01-20 13:35:01 UTC 
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.3.1. 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.