Re: catch replacing useful errorInfo
- From: Donald G Porter <dgp@xxxxxxxx>
- Date: Fri, 31 Aug 2007 10:45:27 -0400
Scrolling back to pick up a couple other points.
tom.rmadilo wrote:
2. This one is difficult to give an example for, maybe this has been
fixed, but the idea is that the body of catch has to be compiled, and
this can fail.
The addition of bytecode compiling in 8.0 was a big step, and it did
take some time to shake *all* the bugs out (some might say we're still
shaking). My guess is that you ran into something ugly like Tcl Bug
705406, and that's made you shy about using [catch]. That bug was a
bad one, but it's fixed now.
5. ... getting all this to work requires full use
of catch, error and return. So using catch is not bad style or bad
programming, it is a big tool which requires a lot of care to apply
correctly,
Developments in Tcl 8.5 should have improved this a fair bit. Take
a look at the updated documentation and TIP 90 for some examples.
http://tmml.sourceforge.net/doc/tcl/return.html
http://tmml.sourceforge.net/doc/tcl/catch.html
http://tip.tcl.tk/90
DGP
.
- Follow-Ups:
- Re: catch replacing useful errorInfo
- From: tom.rmadilo
- Re: catch replacing useful errorInfo
- References:
- catch replacing useful errorInfo
- From: TronyQ
- Re: catch replacing useful errorInfo
- From: tom.rmadilo
- Re: catch replacing useful errorInfo
- From: Donald G Porter
- Re: catch replacing useful errorInfo
- From: tom.rmadilo
- catch replacing useful errorInfo
- Prev by Date: Re: TCL editor recommendation
- Next by Date: Re: Coding Standards
- Previous by thread: Re: catch replacing useful errorInfo
- Next by thread: Re: catch replacing useful errorInfo
- Index(es):
Relevant Pages
|