Hi Simon,

Simon Geard wrote:
>  Have just tried the checker. What it does is great but 
>  limited: my main criticism being that it doesn't apply itself 
>  to files that are 'source' or packages. In practice this is a 
>  strong limitation since I tend to put global configuration 
>  data into a configuration file that is sourced and divide up 
>  main chunks of work into packages. I also use tcllib quite a 
>  lot and any commands from their packages are marked as 
>  unknown. What would be nice would be to have the checker 
>  check everything it can but provide an option for selectively 
>  excluding packages.

The general way to make this work is to provide the full set of Tcl files on
the command line to the Checker.  By default, the Checker operates in a
two-pass mode that does a first scan over all the files to get procs and args,
and then does the checking.  You can also pass package names with -use on the
command line, but Checker does only recognize a limited number of packages
currently.

We have discussed the possibility of improved recognition of packages, and
there is an RFE:
	http://bugs.activestate.com/show_bug.cgi?id=23688
but it's not all that trivial to implement.  To know a package name is not to
know the files associated with a package in Tcl.

  Jeff Hobbs, The Tcl Guy, http://www.ActiveState.com/