Attachment "tclsh.patch" to
ticket [402725ffff]
added by
dgp
2001-08-07 03:45:31.
? solaris
? pfsi.patch
? 219210.diff.5
? 403531.patch
? obj.patch
? pkg.patch
? tclsh.patch
? generic/assoc.patch
? unix/server.tcl
? unix/httpd
? unix/fail.tcl
? unix/.nfs00000000000a4a830000001b
? unix/printenv
Index: doc/tclsh.1
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/tclsh.1,v
retrieving revision 1.4
diff -u -r1.4 tclsh.1
--- doc/tclsh.1 2001/08/06 20:43:05 1.4
+++ doc/tclsh.1 2001/08/06 20:44:07
@@ -123,5 +123,23 @@
if \fBtcl_prompt2\fR isn't set then no prompt is output for
incomplete commands.
+.SH "STANDARD CHANNELS"
+.PP
+.VS
+Tclsh creates three channels by default (on platforms where the
+underlying operating system supports this behaviour) named \fBstdin\fR
+(which is read-only) \fBstdout\fR and \fBstderr\fR (both of which are
+write only.) The intended semantics of their use is very similar to
+that of the equivalently-named file handles in C - input, either as
+typing by the user or data from a file or pipe, comes from
+\fBstdin\fR, output, either to the user's terminal or to a file or
+pipe, goes to \fBstdout\fR, and errors are reported (typically to the
+user's terminal) to \fBstderr\fR - and the channels are
+\fBfconfigure\fRd to support this usage.
+.VE
+
+.SH "SEE ALSO"
+fconfigure(1), tclvars(1)
+
.SH KEYWORDS
argument, interpreter, prompt, script file, shell
