Mass Deface
.
=head1 Changed Internals
The hash code has been refactored to reduce source duplication. The
external interface is unchanged, and aside from the bug fixes described
above, there should be no change in behaviour.
C is now part of the perl API
Some C macros have been tidied. In particular macros which create temporary
local variables now name these variables more defensively, which should
avoid bugs where names clash.
is now always included.
=head1 Configuration and Building
C now invokes callbacks regardless of the value of the variable
they are called for. Previously callbacks were only invoked in the
C branch. This change should only affect platform
maintainers writing configuration hints files.
=head1 Platform Specific Problems
The regression test ext/threads/shared/t/wait.t fails on early RedHat 9
and HP-UX 10.20 due to bugs in their threading implementations.
RedHat users should see https://rhn.redhat.com/errata/RHBA-2003-136.html
and consider upgrading their glibc.
=head1 Known Problems
Detached threads aren't supported on Windows yet, as they may lead to
memory access violation problems.
There is a known race condition opening scripts in C. C
is neither built nor installed by default, and has been deprecated since
perl 5.8.0. You are advised to replace use of suidperl with tools such
as sudo ( http://www.courtesan.com/sudo/ )
We have a backlog of unresolved bugs. Dealing with bugs and bug reports
is unglamorous work; not something ideally suited to volunteer labour,
but that is all that we have.
The perl5 development team are implementing changes to help address this
problem, which should go live in early 2004.
=head1 Future Directions
Code freeze for the next maintenance release (5.8.4) is on March 31st 2004,
with release expected by mid April. Similarly 5.8.5's freeze will be at
the end of June, with release by mid July.
=head1 Obituary
Iain 'Spoon' Truskett, Perl hacker, author of L and
contributor to CPAN, died suddenly on 29th December 2003, aged 24.
He will be missed.
=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://bugs.perl.org. 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
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, will be sent off to perlbug@perl.org to be
analysed by the Perl porting team. You can browse and search
the Perl 5 bugs at http://bugs.perl.org/
=head1 SEE ALSO
The F file for exhaustive details on what changed.
The F file for how to build Perl.
The F file for general stuff.
The F and F files for copyright information.
=cut