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 729135 - Not all Tcl functions are listed in the html output with a particular Tcl line
Not all Tcl functions are listed in the html output with a particular Tcl line
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.8.7-GIT
Other All
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2014-04-28 18:48 UTC by Roland Vossen
Modified: 2014-08-21 17:15 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Roland Vossen 2014-04-28 18:48:38 UTC
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.
Comment 1 Dimitri van Heesch 2014-07-14 18:50:39 UTC
Confirmed. Should be fixed in the next GIT update.
Comment 2 Dimitri van Heesch 2014-08-21 17:15:39 UTC
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).