summaryrefslogtreecommitdiffstats
path: root/generic/tclUtf.c
diff options
context:
space:
mode:
authorjan.nijtmans <nijtmans@users.sourceforge.net>2020-04-15 19:33:20 (GMT)
committerjan.nijtmans <nijtmans@users.sourceforge.net>2020-04-15 19:33:20 (GMT)
commitf480c2471b8d644bb8cf256efcd0f99507fb4d10 (patch)
treeaf9aa731aefad5359bee46b4f612748775d61184 /generic/tclUtf.c
parentcf28c6b1dac27e2a0e39297fc096a656a598fa9b (diff)
downloadtcl-f480c2471b8d644bb8cf256efcd0f99507fb4d10.zip
tcl-f480c2471b8d644bb8cf256efcd0f99507fb4d10.tar.gz
tcl-f480c2471b8d644bb8cf256efcd0f99507fb4d10.tar.bz2
New test command "testutfnext", not used yet in actual test-cases. Being merged up to higher branches. (Thanks, Don!)
Diffstat (limited to 'generic/tclUtf.c')
-rw-r--r--generic/tclUtf.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/generic/tclUtf.c b/generic/tclUtf.c
index fbdba4c..eb9c057 100644
--- a/generic/tclUtf.c
+++ b/generic/tclUtf.c
@@ -666,7 +666,7 @@ Tcl_UtfNext(
* starts a character when characters are read starting at start and
* that character might include the byte src[-1]. The routine will
* examine only those bytes in the range that might be returned.
- * It will not examine the byte *src, and because of that cannot
+ * It will not examine the byte *src, and because of that cannot
* determine for certain in all circumstances whether the character
* that begins with the returned pointer will or will not include
* the byte src[-1]. In the scenario, where src points to the end of
@@ -681,7 +681,7 @@ Tcl_UtfNext(
* prevented from running past the beginning of the string.
*
* In a string where all characters are complete and properly formed,
- * and the value of src points to the first byte of a character,
+ * and the value of src points to the first byte of a character,
* repeated Tcl_UtfPrev calls will step to the starting bytes of
* characters, one character at a time. Within those limitations,
* Tcl_UtfPrev and Tcl_UtfNext are inverses. If either condition cannot