New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

wrong display of tcl function source code using INLINE_SOURCES (Origin: bugzilla #689713) #4978

Closed
doxygen opened this Issue Jul 2, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@doxygen
Owner

doxygen commented Jul 2, 2018

status RESOLVED severity normal in component general for ---
Reported in version 1.8.1.2 on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2012-12-05 16:23:25 +0000, r.zaumseil@freenet.de wrote:

Created attachment 230790
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 tags in the generated html file.

On 2013-01-09 20:31:28 +0000, r.zaumseil@freenet.de wrote:

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

On 2013-01-12 13:00:19 +0000, Dimitri van Heesch wrote:

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.

On 2013-01-20 13:35:01 +0000, Dimitri van Heesch wrote:

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.

@doxygen doxygen closed this Jul 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment