diff options
| author | Aaron Crane <arc@cpan.org> | 2017-03-04 12:50:58 +0000 |
|---|---|---|
| committer | Aaron Crane <arc@cpan.org> | 2017-07-15 19:35:43 +0100 |
| commit | 20ae58f7a9bbf84d043d6e90f5988b6e3ca4ee3d (patch) | |
| tree | 9cc42614061f228b5e0ba9ff22dc8b79f096595d /pod/perlunicode.pod | |
| parent | 36f05cd79a2d07c67e7a1ce57cb3d0a1f632bee7 (diff) | |
| download | perl-20ae58f7a9bbf84d043d6e90f5988b6e3ca4ee3d.tar.gz | |
RT #130907: Fix the Unicode Bug in split " "
Diffstat (limited to 'pod/perlunicode.pod')
| -rw-r--r-- | pod/perlunicode.pod | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/pod/perlunicode.pod b/pod/perlunicode.pod index 43f145918b..ef02b0a1f5 100644 --- a/pod/perlunicode.pod +++ b/pod/perlunicode.pod @@ -1836,6 +1836,17 @@ outside its scope, it could produce strings whose length in characters exceeded that of the right-hand side, where the right-hand side took up more bytes than the correct range endpoint. +=item * + +In L<< C<split>'s special-case whitespace splitting|perlfunc/split >>. + +Starting in Perl 5.28.0, the C<split> function with a pattern specified as +a string containing a single space handles whitespace characters consistently +within the scope of of C<unicode_strings>. Prior to that, or outside its scope, +characters that are whitespace according to Unicode rules but not according to +ASCII rules were treated as field contents rather than field separators when +they appear in byte-encoded strings. + =back You can see from the above that the effect of C<unicode_strings> |