Commit | Line | Data |
---|---|---|
f1d4662f RS |
1 | =encoding utf8 |
2 | ||
3 | =head1 NAME | |
4 | ||
b382629b | 5 | perl5123delta - what is new for perl v5.12.3 |
f1d4662f RS |
6 | |
7 | =head1 DESCRIPTION | |
8 | ||
9 | This document describes differences between the 5.12.2 release and | |
10 | the 5.12.3 release. | |
11 | ||
12 | If you are upgrading from an earlier release such as 5.12.1, first read | |
13 | L<perl5122delta>, which describes differences between 5.12.1 and | |
14 | 5.12.2. The major changes made in 5.12.0 are described in L<perl5120delta>. | |
15 | ||
16 | =head1 Incompatible Changes | |
17 | ||
18 | There are no changes intentionally incompatible with 5.12.2. If any | |
19 | exist, they are bugs and reports are welcome. | |
20 | ||
21 | =head1 Core Enhancements | |
22 | ||
23 | =head2 C<keys>, C<values> work on arrays | |
24 | ||
25 | You can now use the C<keys>, C<values>, C<each> builtin functions on arrays | |
26 | (previously you could only use them on hashes). See L<perlfunc> for details. | |
27 | This is actually a change introduced in perl 5.12.0, but it was missed from | |
28 | that release's perldelta. | |
29 | ||
30 | =head1 Bug Fixes | |
31 | ||
32 | "no VERSION" will now correctly deparse with B::Deparse, as will certain | |
33 | constant expressions. | |
34 | ||
35 | Module::Build should be more reliably pass its tests under cygwin. | |
36 | ||
26c2326b FC |
37 | Lvalue subroutines are again able to return copy-on-write scalars. This |
38 | had been broken since version 5.10.0. | |
f1d4662f RS |
39 | |
40 | =head1 Platform Specific Notes | |
41 | ||
42 | =over 4 | |
43 | ||
44 | =item Solaris | |
45 | ||
46 | A separate DTrace is now build for miniperl, which means that perl can be | |
47 | compiled with -Dusedtrace on Solaris again. | |
48 | ||
49 | =item VMS | |
50 | ||
51 | A number of regressions on VMS have been fixed. In addition to minor cleanup | |
52 | of questionable expressions in F<vms.c>, file permissions should no longer be | |
53 | garbled by the PerlIO layer, and spurious record boundaries should no longer be | |
54 | introduced by the PerlIO layer during output. | |
55 | ||
56 | For more details and discussion on the latter, see: | |
57 | ||
58 | http://www.nntp.perl.org/group/perl.vmsperl/2010/11/msg15419.html | |
59 | ||
60 | =item VOS | |
61 | ||
62 | A few very small changes were made to the build process on VOS to better | |
63 | support the platform. Longer-than-32-character filenames are now supported on | |
64 | OpenVOS, and build properly without IPv6 support. | |
65 | ||
66 | =back | |
67 | ||
68 | =head1 Acknowledgements | |
69 | ||
70 | Perl 5.12.3 represents approximately four months of development since | |
71 | Perl 5.12.2 and contains approximately 2500 lines of changes across | |
72 | 54 files from 16 authors. | |
73 | ||
74 | Perl continues to flourish into its third decade thanks to a vibrant | |
75 | community of users and developers. The following people are known to | |
76 | have contributed the improvements that became Perl 5.12.3: | |
77 | ||
78 | Craig A. Berry, David Golden, David Leadbeater, Father Chrysostomos, Florian | |
79 | Ragwitz, Jesse Vincent, Karl Williamson, Nick Johnston, Nicolas Kaiser, Paul | |
80 | Green, Rafael Garcia-Suarez, Rainer Tammer, Ricardo Signes, Steffen Mueller, | |
81 | Zsbán Ambrus, Ævar Arnfjörð Bjarmason | |
82 | ||
83 | =head1 Reporting Bugs | |
84 | ||
85 | If you find what you think is a bug, you might check the articles | |
86 | recently posted to the comp.lang.perl.misc newsgroup and the perl | |
87 | bug database at http://rt.perl.org/perlbug/ . There may also be | |
88 | information at http://www.perl.org/ , the Perl Home Page. | |
89 | ||
90 | If you believe you have an unreported bug, please run the B<perlbug> | |
91 | program included with your release. Be sure to trim your bug down | |
92 | to a tiny but sufficient test case. Your bug report, along with the | |
93 | output of C<perl -V>, will be sent off to perlbug@perl.org to be | |
94 | analysed by the Perl porting team. | |
95 | ||
96 | If the bug you are reporting has security implications, which make it | |
97 | inappropriate to send to a publicly archived mailing list, then please send | |
98 | it to perl5-security-report@perl.org. This points to a closed subscription | |
1a1f8781 FC |
99 | unarchived mailing list, which includes |
100 | all the core committers, who will be able | |
f1d4662f RS |
101 | to help assess the impact of issues, figure out a resolution, and help |
102 | co-ordinate the release of patches to mitigate or fix the problem across all | |
103 | platforms on which Perl is supported. Please only use this address for | |
104 | security issues in the Perl core, not for modules independently | |
105 | distributed on CPAN. | |
106 | ||
107 | =head1 SEE ALSO | |
108 | ||
109 | The F<Changes> file for an explanation of how to view exhaustive details | |
110 | on what changed. | |
111 | ||
112 | The F<INSTALL> file for how to build Perl. | |
113 | ||
114 | The F<README> file for general stuff. | |
115 | ||
116 | The F<Artistic> and F<Copying> files for copyright information. | |
117 | ||
118 | =cut |