| Christopher Nelson 2004-12-22, 4:04 pm |
| Stephen Kellett wrote:
> In message <1103657932.945890.229480@c13g2000cwb.googlegroups.com>,
> Christopher Nelson <cnelson@nycap.rr.com> writes
>
> Hmm - I think you are answering a different question than the one I
> posed?
You asked about "tools". I interpreteded that more broadly than you
intended but I think my answer still stands...for what I do, the level
of complexity and required reliability, I don't do cover coverage
analysis, etc.
> I wonder if you visited the website I mentioned?
No. Sorry.
> ...
> So how do you perform code coverage,
I don't use it but I would use the TclTest package (I think that's the
name) if I were going to do that. (It's akin to jtest for Java.)
> performance analysis,
The [time] command.
> deadlock detection, flow tracing, memory leak detection using Emacs
> when writing Tcl?
>
> I'm asking because we are considering porting our tools to support
> Tcl and we are interested in what people currently use or would be
> interested in. ...
In a previous life, I did commercial Tcl development where such tools
would have been somewhat useful. Our product was a hybrid Tcl/C
application and we fell back to ... Clarify? ... no ... I don't
remember, some memory tester for detecting leaks, overwrites, and such.
|