Re: Types of software tool used with Tcl - was "What sort of apps are people wri

When it comes to some things like code coverage or flow tracing, I'd
probably use the tools from ActiveState if I needed them. But for other
things (memory analysis is an example) I'd either use the built-in
memory analyzer (it's a compile-time option because it has a noticable
impact on speed) or a tool like Valgrind or Purify.

Deadlock detection isn't usually an issue; I try to write lock-free
code. :^) Tcl makes that easy (inter-thread communication is typically
done by posting messages, and not locking shared resources) Either that
or the application I'm dealing with is based on two or more separate
computers, possibly on different continents, and conventional deadlock
detectors don't work too well. (I'm also lucky if the problem is
expressible in a single programming language.)

Don't get me wrong; having more tools is good. Just not a panacaea.
Donal.