perl5123delta(1)

1PERL5123DELTA(1)       Perl Programmers Reference Guide       PERL5123DELTA(1)
2
3
4

NAME

6       perl5123delta - what is new for perl v5.12.3
7

DESCRIPTION

9       This document describes differences between the 5.12.2 release and the
10       5.12.3 release.
11
12       If you are upgrading from an earlier release such as 5.12.1, first read
13       perl5122delta, which describes differences between 5.12.1 and 5.12.2.
14       The major changes made in 5.12.0 are described in perl5120delta.
15

Incompatible Changes

17           There are no changes intentionally incompatible with 5.12.2. If any
18           exist, they are bugs and reports are welcome.
19

Core Enhancements

21   "keys", "values" work on arrays
22       You can now use the "keys", "values", "each" builtin functions on
23       arrays (previously you could only use them on hashes).  See perlfunc
24       for details.  This is actually a change introduced in perl 5.12.0, but
25       it was missed from that release's perldelta.
26

Bug Fixes

28       "no VERSION" will now correctly deparse with B::Deparse, as will
29       certain constant expressions.
30
31       Module::Build should be more reliably pass its tests under cygwin.
32
33       Lvalue subroutines are again able to return copy-on-write scalars.
34       This had been broken since version 5.10.0.
35

Platform Specific Notes

37       Solaris
38           A separate DTrace is now build for miniperl, which means that perl
39           can be compiled with -Dusedtrace on Solaris again.
40
41       VMS A number of regressions on VMS have been fixed.  In addition to
42           minor cleanup of questionable expressions in vms.c, file
43           permissions should no longer be garbled by the PerlIO layer, and
44           spurious record boundaries should no longer be introduced by the
45           PerlIO layer during output.
46
47           For more details and discussion on the latter, see:
48
49               http://www.nntp.perl.org/group/perl.vmsperl/2010/11/msg15419.html
50
51       VOS A few very small changes were made to the build process on VOS to
52           better support the platform.  Longer-than-32-character filenames
53           are now supported on OpenVOS, and build properly without IPv6
54           support.
55

Acknowledgements

57       Perl 5.12.3 represents approximately four months of development since
58       Perl 5.12.2 and contains approximately 2500 lines of changes across 54
59       files from 16 authors.
60
61       Perl continues to flourish into its third decade thanks to a vibrant
62       community of users and developers.  The following people are known to
63       have contributed the improvements that became Perl 5.12.3:
64
65       Craig A. Berry, David Golden, David Leadbeater, Father Chrysostomos,
66       Florian Ragwitz, Jesse Vincent, Karl Williamson, Nick Johnston, Nicolas
67       Kaiser, Paul Green, Rafael Garcia-Suarez, Rainer Tammer, Ricardo
68       Signes, Steffen Mueller, Zsban Ambrus, AEvar Arnfjoerd` Bjarmason
69

Reporting Bugs

71       If you find what you think is a bug, you might check the articles
72       recently posted to the comp.lang.perl.misc newsgroup and the perl bug
73       database at http://rt.perl.org/perlbug/ .  There may also be
74       information at http://www.perl.org/ , the Perl Home Page.
75
76       If you believe you have an unreported bug, please run the perlbug
77       program included with your release.  Be sure to trim your bug down to a
78       tiny but sufficient test case.  Your bug report, along with the output
79       of "perl -V", will be sent off to perlbug@perl.org to be analysed by
80       the Perl porting team.
81
82       If the bug you are reporting has security implications, which make it
83       inappropriate to send to a publicly archived mailing list, then please
84       send it to perl5-security-report@perl.org. This points to a closed
85       subscription unarchived mailing list, which includes all the core
86       committers, who will be able to help assess the impact of issues,
87       figure out a resolution, and help co-ordinate the release of patches to
88       mitigate or fix the problem across all platforms on which Perl is
89       supported. Please only use this address for security issues in the Perl
90       core, not for modules independently distributed on CPAN.
91