> Ah, that looks interesting! Any plans to add a debugger to this? Like in
> TclProDebug or Komodo?
Yes, there are plans to continue with debugging features of alited. Still, classic debugging tools (stop, step into/over, go to cursor etc.) are not in the plans.
FWIK, ActiveState abandoned supporting Tcl totally, so no support of their tools as well.
I'm sure that the classic tools only mess it all up and don't help it, when you come into a really hard bug. While developing alited, there were two cases when I had to use file loggings to catch a stubborn bug (no other methods could help it).
Tcl has its own incredible introspection facilities that have to be used in debugging options of alited.
Already available options are:
- using shells to run Tcl scripts (e.g. powershell.exe in Windows or lxterminal in Linux), with variable arguments passed to scripts
- using Tkcon to run Tcl scripts (both Linux and Windows), with Tkcon's giant introspection
- templates to set stops, puts (incl. [info ...]) and inputs
One of the forum discussion has contributed also to debugging features of alited, namely - how to proper comment out Tcl code at testing/debugging: