summaryrefslogtreecommitdiff
path: root/utf8.c
diff options
context:
space:
mode:
authorJames E Keenan <jkeenan@cpan.org>2022-12-24 20:35:02 +0000
committerJames E Keenan <jkeenan@cpan.org>2022-12-29 09:39:58 -0500
commit0c6362adf0496a5a25d8b78534541f988ac9ce16 (patch)
tree2568e25b5103297354fd1cdd9f80b8ec71871b76 /utf8.c
parentf4ae97d054e8c75132cb621539374553cf48f64d (diff)
downloadperl-0c6362adf0496a5a25d8b78534541f988ac9ce16.tar.gz
Correct typos as per GH 20435
In GH 20435 many typos in our C code were corrected. However, this pull request was not applied to blead and developed merge conflicts. I extracted diffs for the individual modified files and applied them with 'git apply', excepting four files where patch conflicts were reported. Those files were: handy.h locale.c regcomp.c toke.c We can handle these in a subsequent commit. Also, had to run these two programs to keep 'make test_porting' happy: $ ./perl -Ilib regen/uconfig_h.pl $ ./perl -Ilib regen/regcomp.pl regnodes.h
Diffstat (limited to 'utf8.c')
-rw-r--r--utf8.c6
1 files changed, 3 insertions, 3 deletions
diff --git a/utf8.c b/utf8.c
index 7c35fb8c12..91e314261e 100644
--- a/utf8.c
+++ b/utf8.c
@@ -681,7 +681,7 @@ S_does_utf8_overflow(const U8 * const s,
return 1;
}
- /* Here, it could be the overlong malformation, and might not actuallly
+ /* Here, it could be the overlong malformation, and might not actually
* overflow if you were to calculate it out.
*
* See if it actually is overlong */
@@ -1511,7 +1511,7 @@ Perl__utf8n_to_uvchr_msgs_helper(const U8 *s,
/* A well-formed UTF-8 character, as the vast majority of calls to this
* function will be for, has this expected length. For efficiency, set
- * things up here to return it. It will be overriden only in those rare
+ * things up here to return it. It will be overridden only in those rare
* cases where a malformation is found */
if (retlen) {
*retlen = expectlen;
@@ -1710,7 +1710,7 @@ Perl__utf8n_to_uvchr_msgs_helper(const U8 *s,
* uv contains the code point the input sequence
* represents; or if there is a problem that prevents
* a well-defined value from being computed, it is
- * some subsitute value, typically the REPLACEMENT
+ * some substitute value, typically the REPLACEMENT
* CHARACTER.
* s0 points to the first byte of the character
* s points to just after where we left off processing