SJS wrote:
begin quoting Lan Barnes as of Tue, Mar 25, 2008 at 03:16:59PM -0700:
On Tue, March 25, 2008 3:09 pm, Andrew Lentvorski wrote:
[chop]
Are you *sure* Tcl works that way? Is there no way to change that? I
find it hard to believe given that Expect is a Tcl thing. Such behavior
has to have bitten people pretty badly at various points.
I said the tcl script aborts with traceback. I said nothing about the
called program. Presumably (if it was written right) it won't even send
error codes until it's quite done with its own business.
If by "send error codes" you mean "write to stderr", I disagree.
There's a reason that stderr is unbuffered.
Yeah, that's where I was going with this. I can think of quite a few
instances where I want something to appear on stderr long before the
return code indicates an error has happened or the program itself aborts.
I can also think of things like "tar" where I want indication of an
error but still want the underlying program to proceed to completion.
If you catch the error, can you continue monitoring the program in Tcl,
or have all the descriptors been closed? Basically, does Tcl actually
abort the underlying command, does it disconnect from it, or can it
continue monitoring?
-a
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
