I use TDK 5.0.2 on two Linux Fedora core 4 machines but only most recent one (in term of hardware) check warn style messages with -W4 option.
Why ?
Other question : is it possible to configure style indent values (to use 2 instead of 4) or is it hardcoded ?
The only idea I have regarding the two machines is that you are using slightly different builds of TDK 5.0.2 on them (Look at the build number).
Indentation ... Checking ... The value is hard coded to 4.
Andreas.
Thanks for your idea ... but I have installed TclDevKit5.0.2.290359-linux-ix86-threaded.tar.gz package on each machine.
I read TDK doc and find -style-maxsleep option. Is my issue related to it ?
What a shame for the hard coded 4 value... ;-)
There is some other strange style messages : for example I have a variable named 'cpt' that could be set to 0, 1 or 2.
I have a warning if I code 'if {$cpt == 0} ...' related to boolean test but I cannot code 'if {!$cpt}...' because value 2 is not boolean... Do you have a solution to avoid this warning (excerpt #checker exclude...)
Thanks
Patrick
> Thanks for your idea ... but I have installed
> TclDevKit5.0.2.290359-linux-ix86-threaded.tar.gz
> package on each machine.
And no other (older) TDK ?
What does
teapot-pkg show /path/to/tclchecker
report for the two boxes, where /path/to/tclchecker
is the tclchecker you are using, be it by explicit path, or picked by the shell from PATH (which tclchecker).
> I read TDK doc and find -style-maxsleep option.
> Is my issue related to it ?
No, I do not believe so. This option configures something for the checking of 'exp_sleep'.
> Hard coded value 4 ...
Willing to open a feature request for it on our bug tracker ?
> cpt variable ...
You need either #checker exclude in the code, or -suppress on the command line in general. These are the official ways to disable warnings which are unwanted, or false positives. #checker was explicitly added to provide the fine-grained control for this.
Thanks Andreas for your test. I have already check my office PC but I will do this evening the same test at home...
I have open #84390 bug.
Oups ! I am so confused... :-(
I have two versions of TDK (4.0.1 and 5.0.2) on the same machine and symbolic links point at 4.0.1 release.
Thanks
Patrikc