summaryrefslogtreecommitdiff
path: root/pod/perl5100delta.pod
diff options
context:
space:
mode:
authorRafael Garcia-Suarez <rgarciasuarez@gmail.com>2007-12-18 09:51:39 +0000
committerRafael Garcia-Suarez <rgarciasuarez@gmail.com>2007-12-18 09:51:39 +0000
commita3d15f9a2bf22c599dfee4c8fb750856644c6d1f (patch)
tree618bbc3d2b62e25d629446f0575644e5a6118db4 /pod/perl5100delta.pod
parent4e4a88873a7e660d02017ef31d574516d5d3deb6 (diff)
downloadperl-a3d15f9a2bf22c599dfee4c8fb750856644c6d1f.tar.gz
Notes on 5.12 Unicode revamping planned.
Complete the "reporting bug" section of perldelta. p4raw-id: //depot/perl@32636
Diffstat (limited to 'pod/perl5100delta.pod')
-rw-r--r--pod/perl5100delta.pod22
1 files changed, 20 insertions, 2 deletions
diff --git a/pod/perl5100delta.pod b/pod/perl5100delta.pod
index bd0c1b31d6..8485c546c0 100644
--- a/pod/perl5100delta.pod
+++ b/pod/perl5100delta.pod
@@ -1550,15 +1550,33 @@ Stacked filetest operators won't work when the C<filetest> pragma is in
effect, because they rely on the stat() buffer C<_> being populated, and
filetest bypasses stat().
+=head2 UTF-8 problems
+
+The handling of Unicode still is unclean in several places, where it's
+dependent on whether a string is internally flagged as UTF-8. This will
+be made more consistent in perl 5.12, but that won't be possible without
+a certain amount of backwards incompatibility.
+
+=head1 Platform Specific Problems
+
When compiled with g++ and thread support on Linux, it's reported that the
C<$!> stops working correctly. This is related to the fact that the glibc
provides two strerror_r(3) implementation, and perl selects the wrong
one.
-=head1 Platform Specific Problems
-
=head1 Reporting Bugs
+If you find what you think is a bug, you might check the articles
+recently posted to the comp.lang.perl.misc newsgroup and the perl
+bug database at http://rt.perl.org/rt3/ . There may also be
+information at http://www.perl.org/ , the Perl Home Page.
+
+If you believe you have an unreported bug, please run the B<perlbug>
+program included with your release. Be sure to trim your bug down
+to a tiny but sufficient test case. Your bug report, along with the
+output of C<perl -V>, will be sent off to perlbug@perl.org to be
+analysed by the Perl porting team.
+
=head1 SEE ALSO
The F<Changes> file and the perl590delta to perl595delta man pages for