Attachment "docs_tcl_C-func.patch" to
ticket [1022527fff]
added by
mkolesn
2004-09-05 18:31:48.
Index: Alloc.3
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/Alloc.3,v
retrieving revision 1.8
diff -u -r1.8 Alloc.3
--- Alloc.3 9 Oct 2002 09:38:38 -0000 1.8
+++ Alloc.3 5 Sep 2004 07:58:34 -0000
@@ -84,7 +84,7 @@
as macros. Normally, they are synonyms for the corresponding
procedures documented on this page. When Tcl and all modules
calling Tcl are compiled with \fBTCL_MEM_DEBUG\fR defined, however,
-these macros are redefined to be special debugging versions of
+these macros are redefined to be special debugging versions
of these procedures. To support Tcl's memory debugging within a
module, use the macros rather than direct calls to \fBTcl_Alloc\fR, etc.
Index: AssocData.3
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/AssocData.3,v
retrieving revision 1.4
diff -u -r1.4 AssocData.3
--- AssocData.3 24 Apr 2001 20:59:17 -0000 1.4
+++ AssocData.3 3 Sep 2004 19:31:48 -0000
@@ -10,9 +10,7 @@
.TH Tcl_SetAssocData 3 7.5 Tcl "Tcl Library Procedures"
.BS
.SH NAME
-Tcl_GetAssocData, Tcl_SetAssocData, Tcl_DeleteAssocData \- manage
-associations of string keys and user specified data with Tcl
-interpreters.
+Tcl_GetAssocData, Tcl_SetAssocData, Tcl_DeleteAssocData \- manage associations of string keys and user specified data with Tcl interpreters
.SH SYNOPSIS
.nf
\fB#include <tcl.h>\fR
Index: ByteArrObj.3
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/ByteArrObj.3,v
retrieving revision 1.3
diff -u -r1.3 ByteArrObj.3
--- ByteArrObj.3 4 Apr 2001 16:07:20 -0000 1.3
+++ ByteArrObj.3 5 Sep 2004 08:33:20 -0000
@@ -50,7 +50,7 @@
\fBbinary\fR command. In Tcl, an array of bytes is not equivalent to a
string. Conceptually, a string is an array of Unicode characters, while a
byte-array is an array of 8-bit quantities with no implicit meaning.
-Accesser functions are provided to get the string representation of a
+Accessor functions are provided to get the string representation of a
byte-array or to convert an arbitrary object to a byte-array. Obtaining the
string representation of a byte-array object (by calling
\fBTcl_GetStringFromObj\fR) produces a properly formed UTF-8 sequence with a
Index: ChnlStack.3
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/ChnlStack.3,v
retrieving revision 1.5
diff -u -r1.5 ChnlStack.3
--- ChnlStack.3 16 Jul 2004 20:11:13 -0000 1.5
+++ ChnlStack.3 5 Sep 2004 09:55:52 -0000
@@ -10,7 +10,7 @@
.BS
'\" Note: do not modify the .SH NAME line immediately below!
.SH NAME
-Tcl_StackChannel, Tcl_UnstackChannel, Tcl_GetStackedChannel, Tcl_GetTopChannel \- stack an I/O channel on top of another, and undo it
+Tcl_StackChannel, Tcl_UnstackChannel, Tcl_GetStackedChannel, Tcl_GetTopChannel \- manipulate a stack of I/O channels
.SH SYNOPSIS
.nf
.nf
Index: CrtChannel.3
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/CrtChannel.3,v
retrieving revision 1.17
diff -u -r1.17 CrtChannel.3
--- CrtChannel.3 15 Jul 2004 20:46:49 -0000 1.17
+++ CrtChannel.3 5 Sep 2004 10:04:36 -0000
@@ -261,8 +261,8 @@
this function whenever the channel handlers need to be called for the
channel. See \fBWATCHPROC\fR below for more details.
.PP
-\fBTcl_BadChannelOption\fR is called from driver specific set or get option
-procs to generate a complete error message.
+\fBTcl_BadChannelOption\fR is called from driver-specific \fIsetOptionProc\fR or
+\fIgetOptionProc\fR to generate a complete error message.
.PP
\fBTcl_ChannelBuffered\fR returns the number of bytes of input
currently buffered in the internal buffer (push back area) of the
@@ -350,7 +350,7 @@
.PP
The change to the structures was made in such a way that standard channel
types are binary compatible. However, channel types that use stacked
-channels (ie: TLS, Trf) have new versions to correspond to the above change
+channels (i.e. TLS, Trf) have new versions to correspond to the above change
since the previous code for stacked channels had problems.
.SH TYPENAME
@@ -463,9 +463,9 @@
\fIinterp\fR is not NULL, the procedure should store an error message
in the interpreter's result.
.PP
-These value can be retrieved with \fBTcl_ChannelCloseProc\fR or
-\fBTcl_ChannelClose2Proc\fR, which returns a pointer to the respective
-function.
+The \fIcloseProc\fR and \fIclose2Proc\fR values can be retrieved with
+\fBTcl_ChannelCloseProc\fR or \fBTcl_ChannelClose2Proc\fR, which return
+a pointer to the respective function.
.SH INPUTPROC
.PP
@@ -790,14 +790,14 @@
.PP
This procedure generates a "bad option" error message in an
(optional) interpreter. It is used by channel drivers when
-a invalid Set/Get option is requested. Its purpose is to concatenate
+an invalid Set/Get option is requested. Its purpose is to concatenate
the generic options list to the specific ones and factorize
the generic options error message string.
.PP
It always return \fBTCL_ERROR\fR
.PP
An error message is generated in \fIinterp\fR's result object to
-indicate that a command was invoked with the a bad option
+indicate that a command was invoked with a bad option.
The message has the form
.CS
bad option "blah": should be one of
Index: CrtCommand.3
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/CrtCommand.3,v
retrieving revision 1.7
diff -u -r1.7 CrtCommand.3
--- CrtCommand.3 16 Jul 2004 20:46:33 -0000 1.7
+++ CrtCommand.3 5 Sep 2004 08:05:26 -0000
@@ -108,8 +108,8 @@
version 8.1 of Tcl.
.VE
.PP
-\fIProc\fR must return an integer code that is either \fBTCL_OK\fR, \fBTCL_ERROR\fR,
-\fBTCL_RETURN\fR, \fBTCL_BREAK\fR, or \fBTCL_CONTINUE\fR. See the Tcl overview man page
+\fIProc\fR must return an integer code that is one of \fBTCL_OK\fR, \fBTCL_ERROR\fR,
+\fBTCL_RETURN\fR, \fBTCL_BREAK\fR, \fBTCL_CONTINUE\fR. See the Tcl overview man page
for details on what these codes mean. Most normal commands will only
return \fBTCL_OK\fR or \fBTCL_ERROR\fR. In addition, \fIproc\fR must set
the interpreter result to point to a string value;
Index: CrtMathFnc.3
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/CrtMathFnc.3,v
retrieving revision 1.7
diff -u -r1.7 CrtMathFnc.3
--- CrtMathFnc.3 16 Apr 2003 22:29:20 -0000 1.7
+++ CrtMathFnc.3 5 Sep 2004 08:07:40 -0000
@@ -53,7 +53,7 @@
.AP Tcl_MathProc **procPtr out
Points to a variable that will be set to contain a pointer to the
implementation code for the function (or NULL if the function is
-implemented directly in bytecode.)
+implemented directly in bytecode).
.AP ClientData *clientDataPtr out
Points to a variable that will be set to contain the clientData
argument passed to \fITcl_CreateMathFunc\fR when the function was
Index: CrtObjCmd.3
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/CrtObjCmd.3,v
retrieving revision 1.8
diff -u -r1.8 CrtObjCmd.3
--- CrtObjCmd.3 5 May 2004 20:52:32 -0000 1.8
+++ CrtObjCmd.3 5 Sep 2004 08:09:04 -0000
@@ -290,7 +290,7 @@
command isn't deleted or renamed; callers should copy the string if
they need to keep it for a long time.
.PP
-\fBTcl_GetCommandFullName\fR produces the fully-qualified name
+\fBTcl_GetCommandFullName\fR produces the fully qualified name
of a command from a command token.
The name, including all namespace prefixes,
is appended to the object specified by \fIobjPtr\fP.
Index: CrtTimerHdlr.3
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/CrtTimerHdlr.3,v
retrieving revision 1.2
diff -u -r1.2 CrtTimerHdlr.3
--- CrtTimerHdlr.3 14 Sep 1998 18:39:47 -0000 1.2
+++ CrtTimerHdlr.3 5 Sep 2004 08:10:32 -0000
@@ -11,8 +11,7 @@
.TH Tcl_CreateTimerHandler 3 7.5 Tcl "Tcl Library Procedures"
.BS
.SH NAME
-Tcl_CreateTimerHandler, Tcl_DeleteTimerHandler \- call a procedure at a
-given time
+Tcl_CreateTimerHandler, Tcl_DeleteTimerHandler \- call a procedure at a given time
.SH SYNOPSIS
.nf
\fB#include <tcl.h>\fR
@@ -30,7 +29,7 @@
.AP ClientData clientData in
Arbitrary one-word value to pass to \fIproc\fR.
.AP Tcl_TimerToken token in
-Token for previously-created timer handler (the return value
+Token for previously created timer handler (the return value
from some previous call to \fBTcl_CreateTimerHandler\fR).
.BE
@@ -63,7 +62,7 @@
what to do in \fIproc\fR.
.PP
\fBTcl_DeleteTimerHandler\fR may be called to delete a
-previously-created timer handler. It deletes the handler
+previously created timer handler. It deletes the handler
indicated by \fItoken\fR so that no call to \fIproc\fR
will be made; if that handler no longer exists
(e.g. because the time period has already elapsed and \fIproc\fR
Index: DictObj.3
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/DictObj.3,v
retrieving revision 1.2
diff -u -r1.2 DictObj.3
--- DictObj.3 26 Apr 2004 09:47:18 -0000 1.2
+++ DictObj.3 5 Sep 2004 08:51:26 -0000
@@ -11,7 +11,7 @@
.BS
'\" Note: do not modify the .SH NAME line immediately below!
.SH NAME
-Tcl_NewDictObj, Tcl_DictObjPut, Tcl_DictObjGet, Tcl_DictObjRemove, Tcl_DictObjSize, Tcl_DictObjFirst, Tcl_DictObjNext, Tcl_DictObjDone, Tcl_DictObjPutKeyList, Tcl_DictObjRemoveKeyList \- manipulate Tcl objects as dictionaries
+Tcl_NewDictObj, Tcl_DictObjPut, Tcl_DictObjGet, Tcl_DictObjRemove, Tcl_DictObjSize, Tcl_DictObjFirst, Tcl_DictObjNext, Tcl_DictObjDone, Tcl_DictObjPutKeyList, Tcl_DictObjRemoveKeyList \- manipulate Tcl dictionary objects
.SH SYNOPSIS
.nf
\fB#include <tcl.h>\fR
@@ -77,7 +77,7 @@
.AP Tcl_DictSearch *searchPtr in/out
Pointer to record to use to keep track of progress in enumerating all
key/value pairs in a dictionary. The contents of the record will be
-initialised by the call to \fBTcl_DictObjFirst\fR. If the enumerating
+initialized by the call to \fBTcl_DictObjFirst\fR. If the enumerating
is to be terminated before all values in the dictionary have been
returned, the search record \fImust\fR be passed to
\fBTcl_DictObjDone\fR to enable the internal locks to be released.
@@ -97,10 +97,10 @@
.SH DESCRIPTION
.PP
-Tcl dict objects have an internal representation that supports
+Tcl dictionary objects have an internal representation that supports
efficient mapping from keys to values.
The procedures described in this man page are used to
-create, modify, index, and iterate over Tcl dict objects from C code.
+create, modify, index, and iterate over Tcl dictionary objects from C code.
.PP
\fBTcl_NewDictObj\fR creates a new, empty dictionary object. The
string representation of the object will be invalid, and the reference
@@ -130,7 +130,7 @@
converted to a dictionary.
.PP
\fBTcl_DictObjSize\fR updates the given variable with the number of
-key/value pairs currently in the given dictionary.The result of this
+key/value pairs currently in the given dictionary. The result of this
procedure is TCL_OK, or TCL_ERROR if the \fIdictPtr\fR cannot be
converted to a dictionary.
.PP
@@ -146,7 +146,7 @@
termination of the iteration instead (which Tcl scripts cannot trigger
via the \fBdict\fR command.) The \fIsearchPtr\fR argument points to a
piece of context that is used to identify which particular iteration
-is being performed, and is initialised by the call to
+is being performed, and is initialized by the call to
\fBTcl_DictObjFirst\fR. The \fIdonePtr\fR argument points to a
variable that is updated to be zero of there are further key/value
pairs to be iterated over, or non-zero if the iteration is complete.
@@ -226,4 +226,4 @@
.SH "SEE ALSO"
Tcl_NewObj, Tcl_DecrRefCount, Tcl_IncrRefCount, Tcl_InitObjHashTable
.SH KEYWORDS
-dict, dict object, dictionary, hash table, iteration, object
+dict, dictionary, dictionary object, hash table, iteration, object
Index: DoubleObj.3
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/DoubleObj.3,v
retrieving revision 1.2
diff -u -r1.2 DoubleObj.3
--- DoubleObj.3 14 Sep 1998 18:39:48 -0000 1.2
+++ DoubleObj.3 5 Sep 2004 08:53:18 -0000
@@ -25,7 +25,7 @@
.SH ARGUMENTS
.AS Tcl_Interp doubleValue in/out
.AP double doubleValue in
-A double-precision floating point value used to initialize or set a double object.
+A double-precision floating-point value used to initialize or set a double object.
.AP Tcl_Obj *objPtr in/out
For \fBTcl_SetDoubleObj\fR, this points to the object to be converted
to double type.
@@ -50,7 +50,7 @@
will create a new object of double type
or modify an existing object to have double type.
Both of these procedures set the object to have the
-double-precision floating point value given by \fIdoubleValue\fR;
+double-precision floating-point value given by \fIdoubleValue\fR;
\fBTcl_NewDoubleObj\fR returns a pointer to a newly created object
with reference count zero.
Both procedures set the object's type to be double
Index: Encoding.3
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/Encoding.3,v
retrieving revision 1.15
diff -u -r1.15 Encoding.3
--- Encoding.3 11 Jun 2004 22:39:28 -0000 1.15
+++ Encoding.3 5 Sep 2004 08:17:28 -0000
@@ -99,7 +99,7 @@
automatically be substituted.
.AP Tcl_EncodingState *statePtr in/out
Used when converting a (generally long or indefinite length) byte stream
-in a piece by piece fashion. The conversion routine stores its current
+in a piece-by-piece fashion. The conversion routine stores its current
state in \fI*statePtr\fR after \fIsrc\fR (the buffer containing the
current piece) has been converted; that state information must be passed
back when converting the next piece of the stream so the conversion
@@ -151,7 +151,7 @@
.SH DESCRIPTION
.PP
\fBTcl_GetEncoding\fR finds an encoding given its \fIname\fR. The name may
-refer to a builtin Tcl encoding, a user-defined encoding registered by
+refer to a built-in Tcl encoding, a user-defined encoding registered by
calling \fBTcl_CreateEncoding\fR, or a dynamically-loadable encoding
file. The return value is a token that represents the encoding and can be
used in subsequent calls to procedures such as \fBTcl_GetEncodingName\fR,
@@ -194,7 +194,7 @@
The destination buffer was not large enough for all of the converted data; as
many characters as could fit were converted though.
.IP \fBTCL_CONVERT_MULTIBYTE\fR 29
-The last fews bytes in the source buffer were the beginning of a multibyte
+The last few bytes in the source buffer were the beginning of a multibyte
sequence, but more bytes were needed to complete this sequence. A
subsequent call to the conversion routine should pass a buffer containing
the unconverted bytes that remained in \fIsrc\fR plus some further bytes
@@ -406,7 +406,7 @@
encoding. An example is \fBbig5\fR, used for Chinese text.
.IP "[3] \fBM\fR"
A multi-byte encoding, where one character may be either one or two bytes long.
-Certain bytes are a lead bytes, indicating that another byte must follow
+Certain bytes are lead bytes, indicating that another byte must follow
and that together the two bytes represent one character. Other bytes are not
lead bytes and represent themselves. An example is \fBshiftjis\fR, used by
many Japanese computers.
Index: Environment.3
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/Environment.3,v
retrieving revision 1.1
diff -u -r1.1 Environment.3
--- Environment.3 4 Apr 2001 21:32:18 -0000 1.1
+++ Environment.3 5 Sep 2004 09:10:22 -0000
@@ -28,7 +28,7 @@
\fBTcl_PutEnv\fR sets an environment variable. The information is
passed in a single string of the form NAME=value. This procedure is
intended to be a stand-in for the UNIX \fBputenv\fR system call. All
-tcl-based applications using \fBputenv\fR should redefine it to
+Tcl-based applications using \fBputenv\fR should redefine it to
\fBTcl_PutEnv\fR so that they will interface properly to the Tcl
runtime.
Index: Eval.3
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/Eval.3,v
retrieving revision 1.15
diff -u -r1.15 Eval.3
--- Eval.3 18 Jul 2003 16:56:41 -0000 1.15
+++ Eval.3 5 Sep 2004 08:13:32 -0000
@@ -71,7 +71,7 @@
.AP char *string in
String forming part of a Tcl script.
.AP va_list argList in
-An argument list which must have been initialised using
+An argument list which must have been initialized using
\fBTCL_VARARGS_START\fR, and cleared using \fBva_end\fR.
.BE
@@ -118,7 +118,7 @@
be executed is supplied as a string instead of an object and no compilation
occurs. The string should be a proper UTF-8 string as converted by
\fBTcl_ExternalToUtfDString\fR or \fBTcl_ExternalToUtf\fR when it is known
-to possibly contain upper ASCII characters who's possible combinations
+to possibly contain upper ASCII characters whose possible combinations
might be a UTF-8 special code. The string is parsed and executed directly
(using \fBTcl_EvalObjv\fR) instead of compiling it and executing the
bytecodes. In situations where it is known that the script will never be
Index: GetIndex.3
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/GetIndex.3,v
retrieving revision 1.11
diff -u -r1.11 GetIndex.3
--- GetIndex.3 18 Jul 2003 16:56:41 -0000 1.11
+++ GetIndex.3 5 Sep 2004 08:23:52 -0000
@@ -93,7 +93,7 @@
\fBTcl_GetIndexFromObjStruct\fR works just like
\fBTcl_GetIndexFromObj\fR, except that instead of treating
\fItablePtr\fR as an array of string pointers, it treats it as the
-first in a series of string ptrs that are spaced apart by \fIoffset\fR
+pointer to first string in a series of strings that are spaced apart by \fIoffset\fR
bytes. This is particularly useful when processing things like
\fBTk_ConfigurationSpec\fR, whose string keys are in the same place in
each of several array elements.
Index: GetOpnFl.3
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/GetOpnFl.3,v
retrieving revision 1.4
diff -u -r1.4 GetOpnFl.3
--- GetOpnFl.3 23 Jan 2002 20:46:01 -0000 1.4
+++ GetOpnFl.3 5 Sep 2004 08:26:34 -0000
@@ -9,7 +9,7 @@
.TH Tcl_GetOpenFile 3 8.0 Tcl "Tcl Library Procedures"
.BS
.SH NAME
-Tcl_GetOpenFile \- Get a standard IO File * handle from a channel. (Unix only)
+Tcl_GetOpenFile \- Return a FILE * for a channel registered in the given interpreter (Unix only)
.SH SYNOPSIS
.nf
\fB#include <tcl.h>\fR
Index: Hash.3
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/Hash.3,v
retrieving revision 1.13
diff -u -r1.13 Hash.3
--- Hash.3 21 Apr 2004 21:33:38 -0000 1.13
+++ Hash.3 5 Sep 2004 08:29:14 -0000
@@ -255,7 +255,7 @@
.IP \fBTCL_HASH_KEY_RANDOMIZE_HASH\fR 25
There are some things, pointers for example which don't hash well
because they do not use the lower bits. If this flag is set then the
-hash table will attempt to rectify this by randomising the bits and
+hash table will attempt to rectify this by randomizing the bits and
then using the upper N bits as the index into the table.
.VS 8.5 br
.IP \fBTCL_HASH_KEY_SYSTEM_HASH\fR 25
@@ -290,7 +290,7 @@
it returns 1.
.PP
The \fIallocEntryProc\fR member contains the address of a function
-called to allocate space for an entry and initialise the key.
+called to allocate space for an entry and initialize the key.
.CS
typedef Tcl_HashEntry *(Tcl_AllocHashEntryProc) (
Tcl_HashTable *\fItablePtr\fR, VOID *\fIkeyPtr\fR);
Index: IntObj.3
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/IntObj.3,v
retrieving revision 1.3
diff -u -r1.3 IntObj.3
--- IntObj.3 15 Feb 2002 14:28:47 -0000 1.3
+++ IntObj.3 5 Sep 2004 08:57:18 -0000
@@ -63,7 +63,7 @@
and \fBTcl_GetWideIntFromObj\fR, this refers to the object from which
to get an integer or long integer value; if \fIobjPtr\fR does not
already point to an integer object (or a wide integer object in the
-case of \fBTcl_SetWideIntObj\fR and \fBTcl_GetWideIntFromObj\fR,) an
+case of \fBTcl_SetWideIntObj\fR and \fBTcl_GetWideIntFromObj\fR), an
.VE 8.4
attempt will be made to convert it to one.
.AP Tcl_Interp *interp in/out
Index: Interp.3
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/Interp.3,v
retrieving revision 1.3
diff -u -r1.3 Interp.3
--- Interp.3 14 Apr 2000 23:01:51 -0000 1.3
+++ Interp.3 5 Sep 2004 08:31:32 -0000
@@ -30,7 +30,7 @@
The \fBTcl_CreateInterp\fR procedure returns a pointer to a Tcl_Interp
structure. This pointer is then passed into other Tcl procedures
to process commands in the interpreter and perform other operations
-on the interpreter. Interpreter structures contain many many fields
+on the interpreter. Interpreter structures contain many fields
that are used by Tcl, but only three that may be accessed by
clients: \fIresult\fR, \fIfreeProc\fR, and \fIerrorLine\fR.
.PP
Index: Namespace.3
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/Namespace.3,v
retrieving revision 1.3
diff -u -r1.3 Namespace.3
--- Namespace.3 1 Jul 2004 07:59:22 -0000 1.3
+++ Namespace.3 5 Sep 2004 08:01:24 -0000
@@ -76,7 +76,7 @@
existing commands.
.AP Tcl_Namespace *contextNsPtr in
The location in the namespace hierarchy where the search for a
-namspace or command should be conducted relative to when the search
+namespace or command should be conducted relative to when the search
term is not rooted at the global namespace. NULL indicates the
current namespace.
.AP int flags in
Index: Object.3
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/Object.3,v
retrieving revision 1.6
diff -u -r1.6 Object.3
--- Object.3 22 Oct 2002 12:16:53 -0000 1.6
+++ Object.3 5 Sep 2004 09:00:04 -0000
@@ -153,7 +153,7 @@
.PP
The \fIinternalRep\fR union member holds
an object's internal representation.
-This is either a (long) integer, a double-precision floating point number,
+This is either a (long) integer, a double-precision floating-point number,
a pointer to a value containing additional information
needed by the object's type to represent the object,
or two arbitrary pointers.
@@ -265,7 +265,7 @@
The string representation of \fIx\fR's object is needed
and is recomputed.
The string representation is now \fB124\fR.
-and both representations are again valid.
+And both representations are again valid.
.SH "STORAGE MANAGEMENT OF OBJECTS"
.PP
@@ -283,7 +283,7 @@
An object shared by different code or data structures has
\fIrefCount\fR greater than 1.
Incrementing an object's reference count ensures that
-it won't be freed too early or have its value change accidently.
+it won't be freed too early or have its value change accidentally.
.PP
As an example, the bytecode interpreter shares argument objects
between calling and called Tcl procedures to avoid having to copy objects.
@@ -330,7 +330,7 @@
must check whether the variable's object is shared before
incrementing the integer in its internal representation.
If it is shared, it needs to duplicate the object
-in order to avoid accidently changing values in other data structures.
+in order to avoid accidentally changing values in other data structures.
.SH "SEE ALSO"
Tcl_ConvertToType, Tcl_GetIntFromObj, Tcl_ListObjAppendElement, Tcl_ListObjIndex, Tcl_ListObjReplace, Tcl_RegisterObjType
Index: ObjectType.3
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/ObjectType.3,v
retrieving revision 1.8
diff -u -r1.8 ObjectType.3
--- ObjectType.3 18 Jun 2004 15:17:58 -0000 1.8
+++ ObjectType.3 5 Sep 2004 09:02:36 -0000
@@ -45,7 +45,7 @@
.SH DESCRIPTION
.PP
The procedures in this man page manage Tcl object types.
-The are used to register new object types,
+They are used to register new object types,
look up types,
and force conversions from one type to another.
.PP
@@ -126,7 +126,7 @@
of \fIobjPtr\fR's old type;
it does this by calling the old type's \fIfreeIntRepProc\fR
if it is not NULL.
-As an example, the \fIsetFromAnyProc\fR for the builtin Tcl integer type
+As an example, the \fIsetFromAnyProc\fR for the built-in Tcl integer type
gets an up-to-date string representation for \fIobjPtr\fR
by calling \fBTcl_GetStringFromObj\fR.
It parses the string to obtain an integer and,
@@ -152,7 +152,7 @@
Storage for the byte array must be allocated in the heap by \fBTcl_Alloc\fR
or \fBckalloc\fR. Note that \fIupdateStringProc\fRs must allocate
enough storage for the string's bytes and the terminating null byte.
-The \fIupdateStringProc\fR for Tcl's builtin list type, for example,
+The \fIupdateStringProc\fR for Tcl's built-in list type, for example,
builds an array of strings for each element object
and then calls \fBTcl_Merge\fR
to construct a string with proper Tcl list structure.
@@ -171,7 +171,7 @@
copying its internal representation means.
For example, the \fIdupIntRepProc\fR for the Tcl integer type
simply copies an integer.
-The builtin list type's \fIdupIntRepProc\fR
+The built-in list type's \fIdupIntRepProc\fR
allocates a new array that points at the original element objects;
the elements are shared between the two lists
(and their reference counts are incremented to reflect the new references).
Index: Panic.3
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/Panic.3,v
retrieving revision 1.4
diff -u -r1.4 Panic.3
--- Panic.3 22 Jan 2004 03:03:16 -0000 1.4
+++ Panic.3 5 Sep 2004 09:04:52 -0000
@@ -47,7 +47,7 @@
\fIformat\fR argument is a format string describing how to format the
remaining arguments \fIarg\fR into an error message, according to the
same formatting rules used by the \fBprintf\fR family of functions. The
-same formatting rules are also used by the builtin Tcl command
+same formatting rules are also used by the built-in Tcl command
\fBformat\fR.
.PP
In a freshly loaded Tcl library, \fBTcl_Panic\fR prints the formatted
Index: ParseCmd.3
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/ParseCmd.3,v
retrieving revision 1.13
diff -u -r1.13 ParseCmd.3
--- ParseCmd.3 9 Mar 2004 12:59:04 -0000 1.13
+++ ParseCmd.3 5 Sep 2004 09:08:56 -0000
@@ -356,7 +356,7 @@
\fBTCL_TOKEN_OPERATOR\fR
The token describes one operator of an expression
such as \fB&&\fR or \fBhypot\fR.
-An \fBTCL_TOKEN_OPERATOR\fR token is always preceded by a
+A \fBTCL_TOKEN_OPERATOR\fR token is always preceded by a
\fBTCL_TOKEN_SUB_EXPR\fR token
that describes the operator and its operands;
the \fBTCL_TOKEN_SUB_EXPR\fR token's \fInumComponents\fR field
Index: PrintDbl.3
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/PrintDbl.3,v
retrieving revision 1.2
diff -u -r1.2 PrintDbl.3
--- PrintDbl.3 14 Sep 1998 18:39:49 -0000 1.2
+++ PrintDbl.3 5 Sep 2004 08:29:56 -0000
@@ -29,7 +29,7 @@
.AP double value in
Floating-point value to be converted.
.AP char *dst out
-Where to store string representing \fIvalue\fR. Must have at
+Where to store string representing the \fIvalue\fR. Must have at
least TCL_DOUBLE_SPACE characters of storage.
.BE
Index: RecEvalObj.3
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/RecEvalObj.3,v
retrieving revision 1.3
diff -u -r1.3 RecEvalObj.3
--- RecEvalObj.3 24 Jul 2000 00:03:02 -0000 1.3
+++ RecEvalObj.3 5 Sep 2004 09:11:44 -0000
@@ -44,7 +44,7 @@
you should invoke \fBTcl_EvalObjEx\fR instead of \fBTcl_RecordAndEvalObj\fR.
Normally \fBTcl_RecordAndEvalObj\fR is only called with top-level
commands typed by the user, since the purpose of history is to
-allow the user to re-issue recently-invoked commands.
+allow the user to re-issue recently invoked commands.
If the \fIflags\fR argument contains the TCL_NO_EVAL bit then
the command is recorded without being evaluated.
Index: RecordEval.3
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/RecordEval.3,v
retrieving revision 1.4
diff -u -r1.4 RecordEval.3
--- RecordEval.3 16 Jan 2002 06:02:33 -0000 1.4
+++ RecordEval.3 5 Sep 2004 09:13:28 -0000
@@ -41,7 +41,7 @@
you should invoke \fBTcl_Eval\fR instead of \fBTcl_RecordAndEval\fR.
Normally \fBTcl_RecordAndEval\fR is only called with top-level
commands typed by the user, since the purpose of history is to
-allow the user to re-issue recently-invoked commands.
+allow the user to re-issue recently invoked commands.
If the \fIflags\fR argument contains the TCL_NO_EVAL bit then
the command is recorded without being evaluated.
.PP
Index: RegConfig.3
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/RegConfig.3,v
retrieving revision 1.2
diff -u -r1.2 RegConfig.3
--- RegConfig.3 9 Jun 2003 22:49:13 -0000 1.2
+++ RegConfig.3 5 Sep 2004 09:48:42 -0000
@@ -16,7 +16,7 @@
\fB#include <tcl.h>\fR
.sp
void
-\fBTcl_RegisterConfig\fR(\fIinterp,pkgName,configuration,valEncoding\fR)
+\fBTcl_RegisterConfig\fR(\fIinterp, pkgName, configuration, valEncoding\fR)
.sp
.SH ARGUMENTS
.AP Tcl_Interp *interp in
@@ -34,7 +34,7 @@
Refers to an array of Tcl_Config entries containing the information
embedded in the binary library. Must not be NULL. The end of the array
-is signaled by either a key identical to NULL, or a key refering to
+is signaled by either a key identical to NULL, or a key referring to
the empty string.
.AP "CONST char" *valEncoding in
@@ -50,7 +50,7 @@
The function described here has its base in TIP 59 and provides
extensions with support for the embedding of configuration
information into their binary library and the generation of a
-tcl-level interface for querying this information.
+Tcl-level interface for querying this information.
.PP
To embed configuration information into their binary library an
extension has to define a non-volatile array of Tcl_Config entries in
@@ -65,8 +65,8 @@
.PP
The string \fIvalEncoding\fR contains the name of an encoding known to
Tcl. All these names are use only characters in the ASCII subset of
-UTF-8 and are thus implicity in the UTF-8 encoding. It is expected
-that keys are legible english text and therefore using the ASCII
+UTF-8 and are thus implicitly in the UTF-8 encoding. It is expected
+that keys are legible English text and therefore using the ASCII
subset of UTF-8. In other words, they are expected to be in UTF-8
too. The values associated with the keys can be any string
however. For these the contents of \fIvalEncoding\fR define which
@@ -80,7 +80,7 @@
holding this array is never released. This is the meaning behind the
word \fBnon-volatile\fR used earlier. The easiest way to accomplish
this is to define a global static array of Tcl_Config entries. See the
-file "generic/tclPkgConfig.c" in the sources of the tcl core for an
+file "generic/tclPkgConfig.c" in the sources of the Tcl core for an
example.
.PP
When called \fBTcl_RegisterConfig\fR will
@@ -120,4 +120,4 @@
'\" .SH "SEE ALSO"
.SH KEYWORDS
-embedding, configuration, bianry library
+embedding, configuration, binary library
Index: RegExp.3
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/RegExp.3,v
retrieving revision 1.13
diff -u -r1.13 RegExp.3
--- RegExp.3 13 Nov 2002 22:11:40 -0000 1.13
+++ RegExp.3 5 Sep 2004 09:53:38 -0000
@@ -192,15 +192,15 @@
\fBTcl_GetRegExpFromObj\fR returns NULL and leaves an error message in
the interpreter result. The regular expression token can be used as
long as the internal representation of \fIpatObj\fR refers to the
-compiled form. The \fIeflags\fR argument is a bitwise OR of
+compiled form. The \fIeflags\fR argument is a bit-wise OR of
zero or more of the following flags that control the compilation of
\fIpatObj\fR:
.RS 2
.TP
\fBTCL_REG_ADVANCED\fR
Compile advanced regular expressions (`AREs'). This mode corresponds to
-the normal regular expression syntax accepted by the Tcl regexp and
-regsub commands.
+the normal regular expression syntax accepted by the Tcl \fBregexp\fR and
+\fBregsub\fR commands.
.TP
\fBTCL_REG_EXTENDED\fR
Compile extended regular expressions (`EREs'). This mode corresponds
@@ -232,7 +232,7 @@
expressions and `.' never match newline, `^' matches an empty string
after any newline in addition to its normal function, and `$' matches
an empty string before any newline in addition to its normal function.
-\fBREG_NEWLINE\fR is the bitwise OR of \fBREG_NLSTOP\fR and
+\fBREG_NEWLINE\fR is the bit-wise OR of \fBREG_NLSTOP\fR and
\fBREG_NLANCH\fR.
.TP
\fBTCL_REG_NLSTOP\fR
@@ -245,7 +245,7 @@
\fBTCL_REG_NLANCH\fR
Compile for inverse partial newline-sensitive matching,
with the behavior of
-of `^' and `$' (the ``anchors'') affected, but not the behavior of
+`^' and `$' (the ``anchors'') affected, but not the behavior of
`[^' bracket expressions and `.'. In this mode `^' matches an empty string
after any newline in addition to its normal function, and `$' matches
an empty string before any newline in addition to its normal function.
@@ -281,7 +281,7 @@
specified Unicode character index given by \fIoffset\fR. Unlike
\fBTcl_RegExpExec\fR, the behavior of anchors is not affected by the
offset value. Instead the behavior of the anchors is explicitly
-controlled by the \fIeflags\fR argument, which is a bitwise OR of
+controlled by the \fIeflags\fR argument, which is a bit-wise OR of
zero or more of the following flags:
.RS 2
.TP
Index: SetResult.3
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/SetResult.3,v
retrieving revision 1.7
diff -u -r1.7 SetResult.3
--- SetResult.3 25 Jan 2002 20:40:55 -0000 1.7
+++ SetResult.3 5 Sep 2004 09:07:04 -0000
@@ -49,7 +49,7 @@
\fIstring\fR, or \fBTCL_STATIC\fR, \fBTCL_DYNAMIC\fR, or
\fBTCL_VOLATILE\fR.
.AP va_list argList in
-An argument list which must have been initialised using
+An argument list which must have been initialized using
\fBTCL_VARARGS_START\fR, and cleared using \fBva_end\fR.
.BE
@@ -84,7 +84,7 @@
The object's reference count is not incremented;
if the caller needs to retain a long-term pointer to the object
they should use \fBTcl_IncrRefCount\fR to increment its reference count
-in order to keep it from being freed too early or accidently changed.
+in order to keep it from being freed too early or accidentally changed.
.PP
\fBTcl_SetResult\fR
arranges for \fIstring\fR to be the result for the current Tcl
Index: StdChannels.3
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/StdChannels.3,v
retrieving revision 1.8
diff -u -r1.8 StdChannels.3
--- StdChannels.3 15 Nov 2002 15:34:17 -0000 1.8
+++ StdChannels.3 5 Sep 2004 10:06:04 -0000
@@ -50,7 +50,7 @@
1)
A single standard channel is initialized when it is explicitly
specified in a call to \fBTcl_SetStdChannel\fR. The state of the
-other standard channels are unaffected.
+other standard channels is unaffected.
.sp
Missing platform-specific standard channels do not matter here. This
approach is not available at the script level.
Index: StringObj.3
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/StringObj.3,v
retrieving revision 1.16
diff -u -r1.16 StringObj.3
--- StringObj.3 23 Mar 2004 09:01:00 -0000 1.16
+++ StringObj.3 5 Sep 2004 09:03:20 -0000
@@ -114,7 +114,7 @@
.AP "CONST char" *string in
Null-terminated string value to append to \fIobjPtr\fR.
.AP va_list argList in
-An argument list which must have been initialised using
+An argument list which must have been initialized using
\fBTCL_VARARGS_START\fR, and cleared using \fBva_end\fR.
.AP int newLength in
New length for the string value of \fIobjPtr\fR, not including the
Index: SubstObj.3
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/SubstObj.3,v
retrieving revision 1.1
diff -u -r1.1 SubstObj.3
--- SubstObj.3 12 Jul 2001 13:15:09 -0000 1.1
+++ SubstObj.3 5 Sep 2004 09:30:32 -0000
@@ -53,12 +53,12 @@
sequences that look like variable substitutions for Tcl commands are
replaced by the contents of the named variable.
.PP
-When th \fBTCL_SUBST_COMMANDS\fR bit is set in \fIflags\fR, sequences
+When the \fBTCL_SUBST_COMMANDS\fR bit is set in \fIflags\fR, sequences
that look like command substitutions for Tcl commands are replaced by
-the result of evaluating that script. Where an uncaught continue
-exception occurs during the evaluation of a command substitution, an
-empty string is substituted for the command. Where an uncaught break
-exception occurs during the evaluation of a command substitution, the
+the result of evaluating that script. Where an uncaught 'continue
+exception' occurs during the evaluation of a command substitution, an
+empty string is substituted for the command. Where an uncaught 'break
+exception' occurs during the evaluation of a command substitution, the
result of the whole substitution on \fIobjPtr\fR will be truncated at
the point immediately before the start of the command substitution,
and no characters will be added to the result or substitutions
Index: TCL_MEM_DEBUG.3
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/TCL_MEM_DEBUG.3,v
retrieving revision 1.6
diff -u -r1.6 TCL_MEM_DEBUG.3
--- TCL_MEM_DEBUG.3 15 Nov 2002 15:34:17 -0000 1.6
+++ TCL_MEM_DEBUG.3 5 Sep 2004 10:09:42 -0000
@@ -14,7 +14,7 @@
.SH DESCRIPTION
When Tcl is compiled with \fBTCL_MEM_DEBUG\fR defined, a powerful set
-of memory debugging aids are included in the compiled binary. This
+of memory debugging aids is included in the compiled binary. This
includes C and Tcl functions which can aid with debugging
memory leaks, memory allocation overruns, and other memory related
errors.
@@ -27,7 +27,7 @@
.PP
\fBTCL_MEM_DEBUG\fR must be either left defined for all modules or undefined
for all modules that are going to be linked together. If they are not, link
-errors will occur, with either \fBTclDbCkfree\fR and \fBTcl_DbCkalloc\fR or
+errors will occur, with either \fBTcl_DbCkfree\fR and \fBTcl_DbCkalloc\fR or
\fBTcl_Ckalloc\fR and \fBTcl_Ckfree\fR being undefined.
.PP
Once memory debugging support has been compiled into Tcl, the C
Index: Thread.3
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/Thread.3,v
retrieving revision 1.17
diff -u -r1.17 Thread.3
--- Thread.3 26 Apr 2004 09:16:50 -0000 1.17
+++ Thread.3 5 Sep 2004 08:03:58 -0000
@@ -103,7 +103,7 @@
\fIjoinable\fR. This means that another thread can wait for the such
marked thread to exit and join it.
.PP
-Restrictions: On some unix systems the pthread-library does not
+Restrictions: On some Unix systems the pthread-library does not
contain the functionality to specify the stacksize of a thread. The
specified value for the stacksize is ignored on these systems.
Windows currently does not support joinable threads. This
@@ -133,7 +133,7 @@
The storage is automatically deallocated by \fBTcl_FinalizeThread\fR.
.SS "SYNCHRONIZATION AND COMMUNICATION"
Tcl provides \fBTcl_ThreadQueueEvent\fR and \fBTcl_ThreadAlert\fR
-for handling event queueing in multithreaded applications. See
+for handling event queuing in multithreaded applications. See
the \fBNotifier\fR manual page for more information on these procedures.
.PP
A mutex is a lock that is used to serialize all threads through a piece
@@ -170,7 +170,7 @@
not compiling with threads enabled.
.SS INITIALIZATION
.PP
-All of these synchronization objects are self initializing.
+All of these synchronization objects are self-initializing.
They are implemented as opaque pointers that should be NULL
upon first use.
The mutexes and condition variables are
Index: TraceVar.3
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/TraceVar.3,v
retrieving revision 1.8
diff -u -r1.8 TraceVar.3
--- TraceVar.3 5 Aug 2002 03:24:39 -0000 1.8
+++ TraceVar.3 5 Sep 2004 10:11:22 -0000
@@ -346,7 +346,7 @@
.SH "RESTRICTIONS"
.PP
A trace procedure can be called at any time, even when there
-is a partially-formed result in the interpreter's result area. If
+is a partially formed result in the interpreter's result area. If
the trace procedure does anything that could damage this result (such
as calling \fBTcl_Eval\fR) then it must save the original values of
the interpreter's \fBresult\fR and \fBfreeProc\fR fields and restore
Index: Utf.3
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/Utf.3,v
retrieving revision 1.15
diff -u -r1.15 Utf.3
--- Utf.3 18 Jul 2003 22:17:35 -0000 1.15
+++ Utf.3 5 Sep 2004 10:14:44 -0000
@@ -103,7 +103,7 @@
The length of the Unicode string in characters. Must be greater than or
equal to 0.
.AP "Tcl_DString" *dstPtr in/out
-A pointer to a previously-initialized \fBTcl_DString\fR.
+A pointer to a previously initialized \fBTcl_DString\fR.
.AP "unsigned long" num in
The number of characters to compare.
.AP "CONST char" *start in
@@ -140,7 +140,7 @@
.PP
\fBTcl_UtfToUniChar\fR reads one UTF-8 character starting at \fIsrc\fR
and stores it as a Tcl_UniChar in \fI*chPtr\fR. The return value is the
-number of bytes read from \fIsrc\fR.. The caller must ensure that the
+number of bytes read from \fIsrc\fR. The caller must ensure that the
source buffer is long enough such that this routine does not run off the
end and dereference non-existent or random memory; if the source buffer
is known to be null-terminated, this will not happen. If the input is
@@ -149,15 +149,15 @@
0x00ff and return 1.
.PP
\fBTcl_UniCharToUtfDString\fR converts the given Unicode string
-to UTF-8, storing the result in a previously-initialized \fBTcl_DString\fR.
+to UTF-8, storing the result in a previously initialized \fBTcl_DString\fR.
You must specify the length of the given Unicode string.
The return value is a pointer to the UTF-8 representation of the
Unicode string. Storage for the return value is appended to the
end of the \fBTcl_DString\fR.
.PP
\fBTcl_UtfToUniCharDString\fR converts the given UTF-8 string to Unicode,
-storing the result in the previously-initialized \fBTcl_DString\fR.
-you may either specify the length of the given UTF-8 string or "-1",
+storing the result in the previously initialized \fBTcl_DString\fR.
+You may either specify the length of the given UTF-8 string or "-1",
in which case \fBTcl_UtfToUniCharDString\fR uses \fBstrlen\fR to
calculate the length. The return value is a pointer to the Unicode
representation of the UTF-8 string. Storage for the return value
@@ -170,7 +170,7 @@
.PP
\fBTcl_UniCharNcmp\fR and \fBTcl_UniCharNcasecmp\fR correspond to
\fBstrncmp\fR and \fBstrncasecmp\fR, respectively, for Unicode characters.
-They accepts two null-terminated Unicode strings and the number of characters
+They accept two null-terminated Unicode strings and the number of characters
to compare. Both strings are assumed to be at least \fIlen\fR characters
long. \fBTcl_UniCharNcmp\fR compares the two strings character-by-character
according to the Unicode character ordering. It returns an integer greater
Index: WrongNumArgs.3
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/WrongNumArgs.3,v
retrieving revision 1.5
diff -u -r1.5 WrongNumArgs.3
--- WrongNumArgs.3 1 Jul 2002 18:24:39 -0000 1.5
+++ WrongNumArgs.3 5 Sep 2004 10:15:04 -0000
@@ -63,7 +63,7 @@
the abbreviation. If the \fBTcl_WrongNumArgs\fR command finds any
\fIindexObjects\fR in the \fIobjv\fR array it will use the full subcommand
name in the error message instead of the abbreviated name that was
-originally passed in. Using the above example, lets assume that
+originally passed in. Using the above example, let's assume that
\fIbar\fR is actually an abbreviation for \fIbarfly\fR and the object
is now an indexObject because it was passed to
\fBTcl_GetIndexFromObj\fR. In this case the error message would be:
Index: expr.n
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/expr.n,v
retrieving revision 1.13
diff -u -r1.13 expr.n
--- expr.n 24 May 2004 12:47:56 -0000 1.13
+++ expr.n 5 Sep 2004 07:53:30 -0000
@@ -19,7 +19,7 @@
.SH DESCRIPTION
.PP
-Concatenates \fIarg\fR's (adding separator spaces between them),
+Concatenates \fIarg\fRs (adding separator spaces between them),
evaluates the result as a Tcl expression, and returns the value.
The operators permitted in Tcl expressions are a subset of
the operators permitted in C expressions, and they have the
@@ -62,7 +62,7 @@
.PP
Operands may be specified in any of the following ways:
.IP [1]
-As an numeric value, either integer or floating-point.
+As a numeric value, either integer or floating-point.
.IP [2]
As a Tcl variable, using standard \fB$\fR notation.
The variable's value will be used as the operand.
@@ -84,11 +84,10 @@
forms for operands, such as \fBsin($x)\fR. See below for a list of defined
functions.
.LP
-Where substitutions occur above (e.g. inside quoted strings), they
+Where above substitutions occur (e.g. inside quoted strings), they
are performed by the expression's instructions.
-However, an additional layer of substitution may already have
-been performed by the command parser before the expression
-processor was called.
+However, the command parser may already have performed
+one layer of substitution before the expression processor was called.
As discussed below, it is usually best to enclose expressions
in braces to prevent the command parser from performing substitutions
on the contents.
Index: safe.n
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/safe.n,v
retrieving revision 1.5
diff -u -r1.5 safe.n
--- safe.n 17 Mar 2004 18:14:12 -0000 1.5
+++ safe.n 5 Sep 2004 07:55:48 -0000
@@ -209,7 +209,7 @@
to load packages into its own sub-interpreters.
.TP
\fB\-deleteHook\fR \fIscript\fR
-When this option is given an non empty \fIscript\fR, it will be
+When this option is given a non-empty \fIscript\fR, it will be
evaluated in the master with the name of
the safe interpreter as an additional argument
just before actually deleting the safe interpreter.
@@ -288,7 +288,7 @@
The only valid file names arguments
for the \fBsource\fR and \fBload\fR aliases provided to the slave
are path in the form of
-\fB[file join \fR\fItoken filename\fR\fB]\fR (ie, when using the
+\fB[file join \fR\fItoken filename\fR\fB]\fR (i.e., when using the
native file path formats: \fItoken\fR\fB/\fR\fIfilename\fR
on Unix and \fItoken\fR\fB\\\fIfilename\fR on Windows),
where \fItoken\fR is representing one of the directories
@@ -337,7 +337,7 @@
instead of relying on this default mechanism.
.PP
When the \fIaccessPath\fR is changed after the first creation or
-initialization (ie through \fBinterpConfigure -accessPath \fR\fIlist\fR),
+initialization (i.e. through \fBinterpConfigure -accessPath \fR\fIlist\fR),
an \fBauto_reset\fR is automatically evaluated in the safe interpreter
to synchronize its \fBauto_index\fR with the new token list.
Index: tclsh.1
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/tclsh.1,v
retrieving revision 1.9
diff -u -r1.9 tclsh.1
--- tclsh.1 5 Sep 2003 21:52:11 -0000 1.9
+++ tclsh.1 5 Sep 2004 07:56:30 -0000
@@ -93,7 +93,7 @@
since the backslash at the end of the second line causes the third
line to be treated as part of the comment on the second line.
.PP
-You should note that it is also common practise to install tclsh with
+You should note that it is also common practice to install tclsh with
its version number as part of the name. This has the advantage of
allowing multiple versions of Tcl to exist on the same system at once,
but also the disadvantage of making it harder to write scripts that
Index: tcltest.n
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/tcltest.n,v
retrieving revision 1.42
diff -u -r1.42 tcltest.n
--- tcltest.n 18 Feb 2004 01:41:42 -0000 1.42
+++ tcltest.n 5 Sep 2004 10:16:44 -0000
@@ -683,7 +683,7 @@
match none of the patterns in [\fBconfigure -notfile\fR] is generated
and sorted. Then each file will be evaluated in turn. If
[\fBconfigure -singleproc\fR] is true, then each file will
-be [\fBsource\fR]d in the caller's context. If if is false,
+be [\fBsource\fR]d in the caller's context. If it is false,
then a copy of [\fBinterpreter\fR] will be [\fBexec\fR]d to
evaluate each file. The multi-process operation is useful
when testing can cause errors so severe that a process
Index: tclvars.n
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/tclvars.n,v
retrieving revision 1.15
diff -u -r1.15 tclvars.n
--- tclvars.n 17 Mar 2004 18:14:12 -0000 1.15
+++ tclvars.n 5 Sep 2004 10:18:52 -0000
@@ -277,8 +277,8 @@
how much tracing information
is displayed during bytecode compilation.
By default, tcl_traceCompile is zero and no information is displayed.
-Setting tcl_traceCompile to 1 generates a one line summary in stdout
-whenever a procedure or top level command is compiled.
+Setting tcl_traceCompile to 1 generates a one-line summary in stdout
+whenever a procedure or top-level command is compiled.
Setting it to 2 generates a detailed listing in stdout of the
bytecode instructions emitted during every compilation.
This variable is useful in
@@ -294,7 +294,7 @@
how much tracing information
is displayed during bytecode execution.
By default, tcl_traceExec is zero and no information is displayed.
-Setting tcl_traceExec to 1 generates a one line trace in stdout
+Setting tcl_traceExec to 1 generates a one-line trace in stdout
on each call to a Tcl procedure.
Setting it to 2 generates a line of output
whenever any Tcl command is invoked
@@ -302,7 +302,7 @@
Setting it to 3 produces a detailed trace showing the result of
executing each bytecode instruction.
Note that when tcl_traceExec is 2 or 3,
-commands such as set and incr
+commands such as \fBset\fR and \fBincr\fR
that have been entirely replaced by a sequence
of bytecode instructions are not shown.
Setting this variable is useful in
