5 perl5162delta - what is new for perl v5.16.2
9 This document describes differences between the 5.16.1 release and
12 If you are upgrading from an earlier release such as 5.16.0, first read
13 L<perl5161delta>, which describes differences between 5.16.0 and
16 =head1 Incompatible Changes
18 There are no changes intentionally incompatible with 5.16.0
19 If any exist, they are bugs, and we request that you submit a
20 report. See L</Reporting Bugs> below.
22 =head1 Modules and Pragmata
24 =head2 Updated Modules and Pragmata
30 L<Module::CoreList> has been upgraded from version 2.70 to version 2.76.
34 =head1 Configuration and Compilation
38 =item * configuration should no longer be confused by ls colorization
42 =head1 Platform Support
44 =head2 Platform-Specific Notes
50 Configure now always adds -qlanglvl=extc99 to the CC flags on AIX when
51 using xlC. This will make it easier to compile a number of XS-based modules
52 that assume C99 [perl #113778].
56 =head1 Selected Bug Fixes
60 =item * fix /\h/ equivalence with /[\h]/
68 There are no new known problems.
70 =head1 Acknowledgements
72 Perl 5.16.2 represents approximately 2 months of development since Perl
73 5.16.1 and contains approximately 740 lines of changes across 20 files
76 Perl continues to flourish into its third decade thanks to a vibrant
77 community of users and developers. The following people are known to
78 have contributed the improvements that became Perl 5.16.2:
80 Andy Dougherty, Craig A. Berry, Darin McBride, Dominic Hargreaves, Karen
81 Etheridge, Karl Williamson, Peter Martini, Ricardo Signes, Tony Cook.
83 The list above is almost certainly incomplete as it is automatically
84 generated from version control history. In particular, it does not
85 include the names of the (very much appreciated) contributors who
86 reported issues to the Perl bug tracker.
88 For a more complete list of all of Perl's historical contributors,
89 please see the F<AUTHORS> file in the Perl source distribution.
93 If you find what you think is a bug, you might check the articles
94 recently posted to the comp.lang.perl.misc newsgroup and the perl
95 bug database at http://rt.perl.org/perlbug/ . There may also be
96 information at http://www.perl.org/ , the Perl Home Page.
98 If you believe you have an unreported bug, please run the L<perlbug>
99 program included with your release. Be sure to trim your bug down
100 to a tiny but sufficient test case. Your bug report, along with the
101 output of C<perl -V>, will be sent off to perlbug@perl.org to be
102 analysed by the Perl porting team.
104 If the bug you are reporting has security implications, which make it
105 inappropriate to send to a publicly archived mailing list, then please
106 send it to perl5-security-report@perl.org. This points to a closed
107 subscription unarchived mailing list, which includes all the core
108 committers, who will be able to help assess the impact of issues, figure
109 out a resolution, and help co-ordinate the release of patches to
110 mitigate or fix the problem across all platforms on which Perl is
111 supported. Please only use this address for security issues in the Perl
112 core, not for modules independently distributed on CPAN.
116 The F<Changes> file for an explanation of how to view exhaustive details
119 The F<INSTALL> file for how to build Perl.
121 The F<README> file for general stuff.
123 The F<Artistic> and F<Copying> files for copyright information.