Has anyone looked at the warning/errors generated by procheck and frink relating to tcllib and related programs such as tkchat?
there are quite a number of warnings in tkchat, for instance - things like:
bin/tkchat.tcl:1059 (badSticky) invalid stickyness value: should be one or more of nswe grid .logon.ok - .logon.cn -sticky {} -pady 10 ^
I can't tell how many of these are 'features' of procheck, noise from procheck, or real problems - things like
/usr/tcl84/lib/tcllib1.0/uri/uri.tcl:305 (warnPattern) possible unexpected subst itution in pattern ::info procs Split[string totitle $scheme] ^
may be intentional - just can't tell...
I've recently used frink -HJ on tkchat and uri.tcl and fixed any warnings produced there. I don't currently use procheck.
The second example looks like noise to me. The code does what is intended but could look like there is a missing space.
Log in to post a comment.
Has anyone looked at the warning/errors generated by procheck and frink relating to tcllib and related programs such as tkchat?
there are quite a number of warnings in tkchat,
for instance - things like:
bin/tkchat.tcl:1059 (badSticky) invalid stickyness value: should be one or more
of nswe
grid .logon.ok - .logon.cn -sticky {} -pady 10
^
I can't tell how many of these are 'features' of procheck, noise from procheck, or real problems -
things like
/usr/tcl84/lib/tcllib1.0/uri/uri.tcl:305 (warnPattern) possible unexpected subst
itution in pattern
::info procs Split[string totitle $scheme]
^
may be intentional - just can't tell...
I've recently used frink -HJ on tkchat and uri.tcl and fixed any warnings produced there. I don't currently use procheck.
The second example looks like noise to me. The code does what is intended but could look like there is a missing space.