Skip to content
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

Not all Tcl functions are listed in the html output with a particular Tcl line (Origin: bugzilla #729135) #5464

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

Comments

Projects
None yet
1 participant
@doxygen
Copy link
Owner

doxygen commented Jul 2, 2018

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

On 2014-04-28 18:48:38 +0000, Roland Vossen wrote:

When parsing a certain Tcl file, I noted that the majority of Tcl procs did not show up in Doxygens html output. I did some experiments and could drill it down to the following:

<some_file.tcl>
proc foo {} {

if { ($classifier_state == {{bphy} } ) } { OK

    if { ($classifier_state == {{bphy} }) } { ;# NOK
            puts "this proc is always shown in html output"
    }

}

proc bar {} {
puts "this proc is not shown in html output in NOK case"
}

Note the subtle difference between the two 'if' statements: there is an extra space character between a '}' and the ')' in the 'OK' case.

Albert (albert.tests@gmail.com) investigated this phenomenon a bit further:

"What I do see is that an error is emitted saying:
Error 1184 .../some_notok.tcl() at line 2! expected word separator:
A quick test disabling the error message (setting the internal variable myWhite to 0) did have the effect that the foo function is shown, but as I don't know the background of the space requirement I cannot change it."

Albert advised me to file this bug.

On 2014-07-14 18:50:39 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next GIT update.

On 2014-08-21 17:15:39 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.8. 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 (preferrably in the form of a self-contained example).

@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
You can’t perform that action at this time.