Re: Tcl/Tk debugger
- From: "maura.monville@xxxxxxxxx" <maura.monville@xxxxxxxxx>
- Date: 11 Jun 2006 00:30:45 -0700
Thank you.
How does it compare to Komodo which is a commercial product , in terms
of reliability, friendliness, and number of features ?
We started with a few minor corrections to an existing GUI. But then
we realized that the implementation of some new features was actually
much more time- and energy-consuming than it was expected. I've been
missing the lack of a serious idevelopment tool that for compiled
languages is called debugger.
We are now at a turning point. I have to wrap up the solution of the
problems I've been assigned. Then either we change gear or I will
definitely have to get a debugger.
Thanks,
Maura
Ramon Ribó wrote:
Hello,
If you need to debug TCL, try RamDebugger:
http://wiki.tcl.tk/RamDebugger
Ramon Ribó
En Fri, 09 Jun 2006 20:44:05 +0200, maura.monville@xxxxxxxxx
<maura.monville@xxxxxxxxx> escribió:
suchenwi wrote:
Cameron Laird schrieb:
You ask about the concept of a breakpoint in a language
where commands might not be evaluated until run-time. I
assure you it is possible to set a meaningful breakpoint
even in such cases.
Here is an example, allowing introspection and modification of
variables at the place where [breakpoint] is called:
proc breakpoint args {
while 1 {
puts -nonewline "$args% "
flush stdout
gets stdin cmd
if {$cmd eq "c"} break
catch {uplevel 1 $cmd} res
if {$res ne ""} {puts $res}
}
}
So I should intclude this proc in my Tcl fil and call this procedure at
the point where I wish the interpreter to stop .. am I right ?
Can you please provide an example of usage of yor procedure ?
I understand "c" is the way to exit it. But I do not know which
argments to pass to it.
It seems to start a Tcl interactive session from which I can then print
out and perhaps set some variables of interest....
Thank you,
Maura
--
Compass Ing. y Sistemas Dr. Ramon Ribo
http://www.compassis.com ramsan@xxxxxxxxxxxxx
c/ Tuset, 8 7-2 tel. +34 93 218 19 89
08006 Barcelona, Spain fax. +34 93 396 97 46
.
- Follow-Ups:
- Re: Tcl/Tk debugger
- From: Cameron Laird
- Re: Tcl/Tk debugger
- From: Ramon Ribó
- Re: Tcl/Tk debugger
- References:
- Tcl/Tk debugger
- From: maura.monville@xxxxxxxxx
- Re: Tcl/Tk debugger
- From: Cameron Laird
- Re: Tcl/Tk debugger
- From: suchenwi
- Re: Tcl/Tk debugger
- From: maura.monville@xxxxxxxxx
- Re: Tcl/Tk debugger
- From: Ramon Ribó
- Tcl/Tk debugger
- Prev by Date: Re: PHP vs Tcl [Was: Re: why not C syntax
- Next by Date: Re: Tcl/Tk debugger
- Previous by thread: Re: Tcl/Tk debugger
- Next by thread: Re: Tcl/Tk debugger
- Index(es):
Relevant Pages
|