3 perldelta - what is new for perl v5.11.1
7 This document describes differences between the 5.11.0 release and
10 =head1 Incompatible Changes
14 =item The boolkeys op moved to the group of hash ops. This breaks binary compatibility.
17 =item C<Perl_deprecate()> was replaced with a macro that calls C<Perl_ck_warner()>
19 C<Perl_deprecate> was not part of the public API, and did not have a C<deprecate()>
20 shortcut macro defined without C<-DPERL_CORE>. Neither codesearch.google.com nor
21 CPAN::Unpack show any users outside the Perl core.
25 =head1 Core Enhancements
27 =head2 Add C<package NAME VERSION> syntax
29 This patch adds support for setting the $VERSION of a namespace
30 when the namespace is declared with 'package'. It eliminates the
31 need for 'our $VERSION = ...' and similar constructs. E.g.
33 package Foo::Bar 1.23;
34 # $Foo::Bar::VERSION == 1.23
36 There are several advantages to this:
38 * VERSION is parsed in *exactly* the same way as 'use NAME VERSION'
40 * $VERSION is set at compile time
42 * Eliminates '$VERSION = ...' and 'eval $VERSION' clutter
44 * As it requires VERSION to be a numeric literal or v-string
45 literal, it can be statically parsed by toolchain modules
46 without 'eval' the way MM->parse_version does for '$VERSION = ...'
48 * Alpha versions with underscores do not need to be quoted; static
49 parsing will preserve the underscore, but during compilation, Perl
50 will remove underscores as it does for all numeric literals
52 During development of this, there was discussion on #corehackers and
53 elsewhere that this should also allow other metadata to be set such as
54 "status" (stable/alpha) or "author/authority". On reflection, those
55 metadata are not very well defined yet and likely should never be
56 encoded into Perl core parsing so they can be freely changed in the
57 future. (They could perhaps be achieved via a comment on the same line
58 as 'package NAME VERSION'.)
60 Version numbers, however, already have a very specific definition and
61 use defined in the core through 'use NAME VERSION'. This patch merely
62 provides appropriate symmetry for setting $VERSION with the exact same
63 parsing and semantics as 'use'.
65 It does not break old code with only 'package NAME', but code that
66 uses 'package NAME VERSION' will need to be restricted to perl 5.11.X.
67 This is analogous to the change to open() from two-args to three-args.
68 Users requiring the latest Perl will benefit, and perhaps N years from
69 now it will become standard practice when Perl 5.12 is targeted the
70 way that 5.6 is today.
72 The patch does not prevent 'package NAME VERSION' from being used
73 multiple times for the same package with different version numbers, but
74 nothing prevents $VERSION from being modified arbitrarily at runtime,
75 either, so I see no urgen reason to add limitations or warnings so
76 long as Perl uses a global $VERSION variable for package version
79 I am posting this patch to the p5p list for discussion and review. If
80 there seems to be general assent (or lack of dissent), I will go ahead
81 and commit the patch to blead.
84 =head1 Modules and Pragmata
86 =head2 Updated Modules
90 =item Upgrade to Test-Simple-0.94
92 =item Upgrade to Storable-2.21
94 =item Upgrade to Pod-Simple-3.08
96 =item Upgrade to Parse-CPAN-Meta-1.40
98 =item Upgrade to ExtUtils-Manifest-1.57
100 =item Upgrade to ExtUtils-CBuilder-0.260301
102 =item Upgrade to CGI.pm-3.48
104 =item Update CPANPLUS to CPAN version 0.89_02
106 =item Upgrade to threads::shared 1.32
108 =item Update ExtUtils::ParseXS to 2.21
110 =item Upgrade File::Path to 2.08 (and add taint.t test)
112 =item Upgrade Module::CoreList to 2.20
114 =item Updated Object-Accessor to CPAN version 0.36
118 =head1 New Documentation
122 =item L<pod/perlpolicy.pod> extends the "Social contract about contributed modules" into the beginnings of a document on Perl porting policies.
126 =head1 Changes to Existing Documentation
130 =item Documentation for C<$1> in perlvar.pod clarified
134 =head1 Performance Enhancements
138 =item C<if (%foo)> has been optimized to be faster than C<if (keys %foo)>
142 =head1 Installation and Configuration Improvements
144 XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
147 =head2 Platform Specific Changes
151 =item Darwin (Mac OS X)
155 =item Skip testing the be_BY.CP1131 locale on Darwin 10 (Mac OS X 10.6),
158 =item Correct infelicities in the regexp used to identify buggy locales
159 on Darwin 8 and 9 (Mac OS X 10.4 and 10.5, respectively).
167 =item Fix thread library selection [perl #69686]
175 =item Initial support for mingw64 is now available
182 =head1 Selected Bug Fixes
186 =item Perl now properly returns a syntax error instead of segfaulting
187 if C<each>, C<keys> or C<values> is used without an argument
189 =item C<tell()> now fails properly if called without an argument and when no previous file was read
191 C<tell()> now returns C<-1>, and sets errno to C<EBADF>, thus restoring the 5.8.x behaviour
193 =item overload no longer implicitly unsets fallback on repeated 'use overload' lines
195 =item POSIX::strftime() can now handle Unicode characters in the format string.
197 =item The winsock select() implementation now supports all empty C<fd_set>s more correctly.
201 =head1 New or Changed Diagnostics
206 =item The 'syntax' category was removed from 5 warnings that should only be in 'deprecated'.
208 =item Three fatal pack/unpack error messages have been normalized to "panic: %s"
210 =item "Unicode character is illegal" has been rephrased to be more accurate
212 It now reads C<Unicode non-character is illegal in interchange> and the
213 perldiag documentation has been expanded a bit.
215 =item Perl now defaults to issuing a warning if a deprecated language feature is used.
217 To disable this feature in a given lexical scope, you should use C<no
218 warnings 'deprecated';> For information about which language features
219 are deprecated and explanations of various deprecation warnings, please
228 =item Significant cleanups to core tests to ensure that language and
229 interpreter features are not used before they're tested.
231 =item F<t/porting/podcheck.t> automatically checks the well-formedness of
232 POD found in all .pl, .pm and .pod files in the F<MANIFEST>, other than in
233 dual-lifed modules which are primarily maintained outside the Perl core.
235 =item F<t/porting/manifest.t> now tests that all files listed in MANIFEST are present.
239 =head1 Known Problems
241 XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
242 tests that had to be C<TODO>ed for the release would be noted here, unless
243 they were specific to a particular platform (see below).
245 This is a list of some significant unfixed bugs, which are regressions
246 from either 5.10.1 or 5.11.0.
260 =item The Perl 5.11.0 release notes incorrectly described 'delete local'
264 =head1 Acknowledgements
266 XXX The list of people to thank goes here.
269 =head1 Reporting Bugs
271 If you find what you think is a bug, you might check the articles
272 recently posted to the comp.lang.perl.misc newsgroup and the perl
273 bug database at http://rt.perl.org/perlbug/ . There may also be
274 information at http://www.perl.org/ , the Perl Home Page.
276 If you believe you have an unreported bug, please run the B<perlbug>
277 program included with your release. Be sure to trim your bug down
278 to a tiny but sufficient test case. Your bug report, along with the
279 output of C<perl -V>, will be sent off to perlbug@perl.org to be
280 analysed by the Perl porting team.
282 If the bug you are reporting has security implications, which make it
283 inappropriate to send to a publicly archived mailing list, then please send
284 it to perl5-security-report@perl.org. This points to a closed subscription
285 unarchived mailing list, which includes all the core committers, who be able
286 to help assess the impact of issues, figure out a resolution, and help
287 co-ordinate the release of patches to mitigate or fix the problem across all
288 platforms on which Perl is supported. Please only use this address for
289 security issues in the Perl core, not for modules independently
294 The F<Changes> file for an explanation of how to view exhaustive details
297 The F<INSTALL> file for how to build Perl.
299 The F<README> file for general stuff.
301 The F<Artistic> and F<Copying> files for copyright information.
305 This is all changes through 6609e0408cfa30e0d5c739e4c818f8591c88c0bc