summaryrefslogtreecommitdiff
path: root/utf8.c
diff options
context:
space:
mode:
authorKarl Williamson <khw@cpan.org>2016-10-12 19:14:13 -0600
committerKarl Williamson <khw@cpan.org>2016-10-13 11:18:12 -0600
commitaff2be59e4b3bbb62744c92140fb0be47ae32d1c (patch)
treede08acf51bfc8dfa20a2c1d5f13b2c7c843aa180 /utf8.c
parentf4caf2b26940946566282dc266c4d4964d38d036 (diff)
downloadperl-aff2be59e4b3bbb62744c92140fb0be47ae32d1c.tar.gz
perlapi: Fix clause that should have been removed earlier
Diffstat (limited to 'utf8.c')
-rw-r--r--utf8.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/utf8.c b/utf8.c
index 0432bb047f..729650d7db 100644
--- a/utf8.c
+++ b/utf8.c
@@ -848,7 +848,7 @@ Code points above 0x7FFF_FFFF (2**31 - 1) were never specified in any standard,
so using them is more problematic than other above-Unicode code points. Perl
invented an extension to UTF-8 to represent the ones above 2**36-1, so it is
likely that non-Perl languages will not be able to read files that contain
-these that written by the perl interpreter; nor would Perl understand files
+these; nor would Perl understand files
written by something that uses a different extension. For these reasons, there
is a separate set of flags that can warn and/or disallow these extremely high
code points, even if other above-Unicode ones are accepted. These are the