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