summaryrefslogtreecommitdiffstats
path: root/doc/CrtChnlHdlr.3
diff options
context:
space:
mode:
Diffstat (limited to 'doc/CrtChnlHdlr.3')
-rw-r--r--doc/CrtChnlHdlr.36
1 files changed, 4 insertions, 2 deletions
diff --git a/doc/CrtChnlHdlr.3 b/doc/CrtChnlHdlr.3
index 0ecd3c9..affd7e2 100644
--- a/doc/CrtChnlHdlr.3
+++ b/doc/CrtChnlHdlr.3
@@ -35,6 +35,7 @@ the conditions specified by \fImask\fR.
.AP ClientData clientData in
Arbitrary one-word value to pass to \fIproc\fR.
.BE
+
.SH DESCRIPTION
.PP
\fBTcl_CreateChannelHandler\fR arranges for \fIproc\fR to be called in the
@@ -45,9 +46,8 @@ invoked are specified by the \fImask\fR argument.
See the manual entry for \fBfileevent\fR for a precise description of
what it means for a channel to be readable or writable.
\fIProc\fR must conform to the following prototype:
-.PP
.CS
-typedef void \fBTcl_ChannelProc\fR(
+typedef void Tcl_ChannelProc(
ClientData \fIclientData\fR,
int \fImask\fR);
.CE
@@ -83,7 +83,9 @@ so that the channel is no longer readable when the second handler
is invoked.
For this reason it may be useful to use nonblocking I/O on channels
for which there are event handlers.
+
.SH "SEE ALSO"
Notifier(3), Tcl_CreateChannel(3), Tcl_OpenFileChannel(3), vwait(n).
+
.SH KEYWORDS
blocking, callback, channel, events, handler, nonblocking.