Re: [Doxygen-develop] Tcl parsing problem

[Roland V. <rv...@br...>]

Will do that. Thank you Albert.

From: Albert [mailto:alb...@gm...]
Sent: maandag 28 april 2014 20:05
To: Roland Vossen
Cc: dox...@li...; ser...@gm...; di...@st...
Subject: Re: Tcl parsing problem

Hi Roland,
I'm not familiar with the tclscanner and also not really familiar with the tcl language (changes that I made hadn't anything really to do with tcl but more with some general implementation stuff). I had a quick look but could not figure out the problem / the design philosophy behind the requirement of the space.
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.
Best is to file a bug in bugzilla.
Albert

On Mon, Apr 28, 2014 at 10:14 AM, Roland Vossen <rv...@br...<mailto:rv...@br...>> wrote:
Hello Albert,

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 ')'.

Is this something you can look at ?

Thanks, Roland.