On Tue, March 25, 2008 2:14 pm, Andrew Lentvorski wrote: > Lan Barnes wrote: > >> Tcl throws an error if an exec call returns anything on stderr. This >> makes >> perfect sense as long as they're real errors. I can catch them and >> abort >> the program if I don't care what the error is, or parse the error return >> if some errors call for different handling. But if the program is using >> stderr to say "everything's still OK here, boss :-)" I lose that >> flexibility. > > So Tcl actually aborts the *exec* call if something hits stderr? > > If so, that's broken. Badly. > > -a >
A tcl script aborts with traceback on _any_ error. That's by design. You can catch the error and do any damned thing you want with it, including ignoring it altogether. Because that's by design, I will accept "that's broken in my humble opinion." Or <snark attack warning> you can join the Tcl core group (it's open) and lobby for a change. You might recall that a perl script breaks before even executing anything, also by design, on a syntax error. And we must ask ourselves, if it can detect a syntax error, why doesn't it just correct it? ;-) -- Lan Barnes SCM Analyst Linux Guy Tcl/Tk Enthusiast Biodiesel Brewer -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
