The web home for TclPro can be found at:
ActiveState has created the Tcl Dev Kit which include an updated, quality-assured version of TclPro. This product is also part of ASPN Tcl.
TclPro consists of a code checker, GUI debugger (i.e. the debugger has a GUI, rather than being a GUI debugger), a byte-code compiler and wrapper and some extensions (TclX, Expect, [incr Tcl] ...) and tclsh/wish.
Oh... and it's open source these days.
TclPro has a reputation for being tough to build. See notes on building TclPro for more details.
The TclPro debugger is strictly a debugger - it does not contain the ability to edit code and then continue on. Instead, one uses a favorite editor, and then start the app over again.
The TclPro static code checker (procheck) is the piece I LV most frequently use. It, along with frink, provide two tools for analyzing Tcl code and predicting possible problem code.
Try getting the file named FREE_KEYS from ftp://www.tcl.tk/pub/tclpro/download/ and I think you'll have better luck. For the FTP impaired, and for the records of all the great news search engines, I'll include all 671 bytes here.
With the acquisition of Scriptics/Ajuba by Interwoven the TclPro product line has been discontinued and moved into the open source community. The files in this directory require license keys in order to use the development tools (e.g, TclPro Debugger, TclPro Checker, TclPro Compiler, and TclPro Wrapper). Here are keys for different versions. TclPro (Tcl/Tk) Key 1.2 8.0.5 1K14-2207-0H34-1U24-R8ZJ 1.3 8.2.0 1V45-2209-1G37-1U35-R8Y6 1.4.1 8.3.2 1094-320C-1G38-2U24-P8YY If you run the TclPro network license server, the keys are different: TclPro Key for 10 seats 1.2 2N06-0H35-04U2-5R8Y-X2H0 1.3 2M09-1H27-04V2-5P9Z-188S 1.4.1 2M1C-1H28-34U3-4P8Z-DRG2
And for those peeking in, version 1.5 for TclPro was released during 2001, without license key issues.
[Are there any on-line forms of the documentation?]
There are competing products for several of the TclPro modules. ProCheck is one of a handful of static syntax checkers [L1 ], Procomp and prowrap are two of almost a dozen different compilation schemes (How can I compile Tcl type scripts into binary code) in use, at least as many debuggers [...] compete with ProDebug [check spelling]
Check RamDebugger for an alternative of Compiler/IDE
Debugging AOLserver with Tcl Dev Kit is relevant for TclPro too.