diff options
| author | jan.nijtmans <nijtmans@users.sourceforge.net> | 2018-07-10 19:18:17 (GMT) |
|---|---|---|
| committer | jan.nijtmans <nijtmans@users.sourceforge.net> | 2018-07-10 19:18:17 (GMT) |
| commit | ec3c18e54e7411b1a18b2695fac6ce00069849b4 (patch) | |
| tree | a1d6efb47f9187208e5cd4bf8f4a36bd9d4d1e9d /doc/Limit.3 | |
| parent | 9a9c228341c0256a141aa964d570d563e177440c (diff) | |
| download | tcl-ec3c18e54e7411b1a18b2695fac6ce00069849b4.zip tcl-ec3c18e54e7411b1a18b2695fac6ce00069849b4.tar.gz tcl-ec3c18e54e7411b1a18b2695fac6ce00069849b4.tar.bz2 | |
Remove 4 unneeded compatibility macro's, because those functions never return -1 anyway.
Change documentation to use void * in stead of ClientData
Diffstat (limited to 'doc/Limit.3')
| -rw-r--r-- | doc/Limit.3 | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/Limit.3 b/doc/Limit.3 index 5939a80..3aac88a 100644 --- a/doc/Limit.3 +++ b/doc/Limit.3 @@ -83,7 +83,7 @@ the handler returns. Many handlers may be attached to the same interpreter limit; their order of execution is not defined, and they must be identified by \fIhandlerProc\fR and \fIclientData\fR when they are deleted. -.AP ClientData clientData in +.AP void *clientData in Arbitrary pointer-sized word used to pass some context to the \fIhandlerProc\fR function. .AP Tcl_LimitHandlerDeleteProc *deleteProc in @@ -162,7 +162,7 @@ following prototype: .PP .CS typedef void \fBTcl_LimitHandlerProc\fR( - ClientData \fIclientData\fR, + void *\fIclientData\fR, Tcl_Interp *\fIinterp\fR); .CE .PP @@ -179,7 +179,7 @@ following prototype: .PP .CS typedef void \fBTcl_LimitHandlerDeleteProc\fR( - ClientData \fIclientData\fR); + void *\fIclientData\fR); .CE .PP A limit handler may be deleted using \fBTcl_LimitRemoveHandler\fR; the |