Re: [Tclpro-users] Fwd: TclPro checker

[Scott R. <re...@we...>]

Maybe someone else has a better answer.

IIRC, and it's been many years, there are files defining functions in supported C extensions like [incr Tcl] and Expect.  Those files are in the TclPro source tree.  Poke through the code on SourceForge, I thought we had a hidden/unsupported ability to add those yourself.... if not you can add them and rebuild TclPro Checker.  We didn't document it in the public docs, but there might be comments in the code.

You might be able to just add a dummy file that defines those procs as empty and add it to the procheck line.

Alternatively, check out the ActiveState tools.  They picked up the pieces and have done a great job.

-- Scott

(I just fixed the homepage link on the SF tclpro page)



On Jul 25, 2013, at 12:04 AM, Senthil கந்தசாமி wrote:

> 
> Hi,
> 
> I am using TclPro procheck version 1.4
> 
> I just want to know is there a way to tell the procheck the user defined libs and packages
> 
> procheck -verbose -W1 /foo.tcl
> 
> Commands that were called but never defined:
> step_start
> step_result
> ::caat::step_get_global_result
> ::au::result_code
> 
> 
> These are actually procs that are in my lib and package. How to let the prochek  to know this. i.e where can i mention this in procheck, so that it won't report warning or error.
> 
> 
> -- 
> Regards,
> Senthil K
> ------------------------------------------------------------------------------
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk_______________________________________________
> Tclpro-users mailing list
> Tcl...@li...
> https://lists.sourceforge.net/lists/listinfo/tclpro-users