* win/tclWinPipe.c: The pipe channel driver now respects

the -blocking option when closing.  The windows pipe driver
now has the same behavior as the UNIX side.  This change is
to avoid a hung shell when exiting due to open pipes that
refuse to close in a graceful manner.
* doc/open.n: Added a note about -blocking 0 and lack of
exit status as it had never been documented. [Bug 947693]

***POTENTIAL INCOMPATIBILITY***

Scripts that use async pipes on windows, must (like the
UNIX side) set -blocking to 1 before calling [close] to
receive the exit status.

* tests/winPipe.test (winpipe-6.1/2):  added 'fconfigure $f
-blocking 1' so the exit status can be acquired.

1 files changed, 3 insertions, 2 deletions

diff --git a/doc/open.n b/doc/open.n
index 4322dde..003739b 100644
--- a/doc/open.n
+++ b/doc/open.n
@@ -5,7 +5,7 @@
 '\" See the file "license.terms" for information on usage and redistribution
 '\" of this file, and for a DISCLAIMER OF ALL WARRANTIES.
 '\" 
-'\" RCS: @(#) $Id: open.n,v 1.16.2.2 2004/10/27 14:23:57 dkf Exp $
+'\" RCS: @(#) $Id: open.n,v 1.16.2.3 2005/04/19 16:30:21 davygrvy Exp $
 '\" 
 .so man.macros
 .TH open n 8.3 Tcl "Tcl Built-In Commands"
@@ -136,7 +136,8 @@ command, using the channel id returned by \fBopen\fR as argument.
 If the command (or one of the commands) executed in the command
 pipeline returns an error (according to the definition in \fBexec\fR),
 a Tcl error is generated when \fBclose\fR is called on the channel
-(similar to the \fBclose\fR command.)
+unless the pipeline is in non-blocking mode then no exit status is
+returned (a silent \fBclose\fR with -blocking 0).
 .PP
 It is often useful to use the \fBfileevent\fR command with pipelines
 so other processing may happen at the same time as running the command