3 perl5120delta - what is new for perl v5.12.0
5 =head1 XXX - THIS DOCUMENT IS ONLY CURRENT THROUGH PERL5114
11 UPDATED MODULE LIST NEEDS TO BE GENERATED
12 ORDERING NEEDS CHECKING
13 HEAVY COPYEDITING IS NEEDED
18 This document describes differences between the 5.10.0 release and
21 Many of the bug fixes in 5.12.0 were already seen in the 5.10.1
22 maintenance release since the two releases were kept closely
23 coordinated (while 5.12.0 was still called 5.11.something).
25 You can see the list of changes in the 5.10.1 release
26 by reading L<perl5101delta>.
28 =head1 Core Enhancements
32 It is now possible to overload the C<qr//> operator, that is,
33 conversion to regexp, like it was already possible to overload
34 conversion to boolean, string or number of objects. It is invoked when
35 an object appears on the right hand side of the C<=~> operator or when
36 it is interpolated into a regexp. See L<overload>.
38 =head2 Pluggable keywords
40 Extension modules can now cleanly hook into the Perl parser to define
41 new kinds of keyword-headed expression and compound statement. The
42 syntax following the keyword is defined entirely by the extension. This
43 allow a completely non-Perl sublanguage to be parsed inline, with the
44 correct ops cleanly generated. This feature is currently considered
47 See L<perlapi/PL_keyword_plugin> for the mechanism. The Perl core
48 source distribution also includes a new module
49 L<XS::APItest::KeywordRPN>, which implements reverse Polish notation
50 arithmetic via pluggable keywords. This module is mainly used for test
51 purposes, and is not normally installed, but also serves as an example
52 of how to use the new mechanism.
54 =head2 APIs for more internals
56 The lowest layers of the lexer and parts of the pad system now have C
57 APIs available to XS extensions. These are necessary to support proper
58 use of pluggable keywords, but have other uses too. The new APIs are
59 experimental, and only cover a small proportion of what would be
60 necessary to take full advantage of the core's facilities in these
61 areas. It is intended that the Perl 5.13 development cycle will see the
62 addition of a full range of clean, supported interfaces.
64 =head2 Overridable function lookup
66 Where an extension module hooks the creation of rv2cv ops to modify the
67 subroutine lookup process, this now works correctly for bareword
68 subroutine calls. This means that prototypes on subroutines referenced
69 this way will be processed correctly. (Previously bareword subroutine
70 names were initially looked up, for parsing purposes, by an unhookable
71 mechanism, so extensions could only properly influence subroutine names
72 that appeared with an C<&> sigil.)
74 =head2 Unicode version
76 Perl is shipped with the latest Unicode version, 5.2, dated October 2009. See
77 L<http://www.unicode.org/versions/Unicode5.2.0> for details about this release
78 of Unicode. See L<perlunicode> for instructions on installing and using
79 older versions of Unicode.
81 =head2 Unicode properties
83 A concerted effort has been made to update Perl to be in sync with the latest
84 Unicode standard. Changes for this include:
86 Perl can now handle every Unicode character property. A new pod,
87 L<perluniprops>, lists all available non-Unihan character properties. By
88 default the Unihan properties and certain others (deprecated and Unicode
89 internal-only ones) are not exposed. See below for more details on
90 these; there is also a section in the pod listing them, and explaining
91 why they are not exposed.
93 Perl now fully supports the Unicode compound-style of using C<=> and C<:>
94 in writing regular expressions: C<\p{property=value}> and
95 C<\p{property:value}> (both of which mean the same thing).
97 Perl now fully supports the Unicode loose matching rules for text
98 between the braces in C<\p{...}> constructs. In addition, Perl allows
99 underscores between digits of numbers.
101 All the Unicode-defined synonyms for properties and property values are
104 C<qr/\X/>, which matches a Unicode logical character, has been expanded to work
105 better with various Asian languages. It now is defined as an I<extended
106 grapheme cluster>. (See L<http://www.unicode.org/reports/tr29/>).
107 Anything matched previously and that made sense will continue to be
108 matched, but in addition:
114 C<\X> will not break apart a C<S<CR LF>> sequence.
118 C<\X> will now match a sequence which includes the C<ZWJ> and C<ZWNJ> characters.
122 C<\X> will now always match at least one character, including an initial mark.
123 Marks generally come after a base character, but it is possible in Unicode to
124 have them in isolation, and C<\X> will now handle that case, for example at the
125 beginning of a line, or after a C<ZWSP>. And this is the part where C<\X>
126 doesn't match the things that it used to that don't make sense. Formerly, for
127 example, you could have the nonsensical case of an accented LF.
131 C<\X> will now match a (Korean) Hangul syllable sequence, and the Thai and Lao
136 Otherwise, this change should be transparent for the non-affected languages.
138 C<\p{...}> matches using the Canonical_Combining_Class property were
139 completely broken in previous Perls. This is now fixed.
141 In previous Perls, the Unicode C<Decomposition_Type=Compat> property and a
142 Perl extension had the same name, which led to neither matching all the
143 correct values (with more than 100 mistakes in one, and several thousand
144 in the other). The Perl extension has now been renamed to be
145 C<Decomposition_Type=Noncanonical> (short: C<dt=noncanon>). It has the same
146 meaning as was previously intended, namely the union of all the
147 non-canonical Decomposition types, with Unicode C<Compat> being just one of
150 C<\p{Uppercase}> and C<\p{Lowercase}> have been brought into line with the
151 Unicode definitions. This means they each match a few more characters
154 C<\p{Cntrl}> now matches the same characters as C<\p{Control}>. This means it
155 no longer will match Private Use (gc=co), Surrogates (gc=cs), nor Format
156 (gc=cf) code points. The Format code points represent the biggest
157 possible problem. All but 36 of them are either officially deprecated
158 or strongly discouraged from being used. Of those 36, likely the most
159 widely used are the soft hyphen (U+00AD), and BOM, ZWSP, ZWNJ, WJ, and
160 similar characters, plus bidirectional controls.
162 C<\p{Alpha}> now matches the same characters as C<\p{Alphabetic}>. The Perl
163 definition included a number of things that aren't really alpha (all
164 marks), while omitting many that were. As a direct consequence, the
165 definitions of C<\p{Alnum}> and C<\p{Word}> which depend on Alpha also change
168 C<\p{Word}> also now doesn't match certain characters it wasn't supposed
169 to, such as fractions.
171 C<\p{Print}> no longer matches the line control characters: Tab, LF, CR,
172 FF, VT, and NEL. This brings it in line with standards and the documentation.
174 C<\p{Decomposition_Type=Canonical}> now includes the Hangul syllables.
176 C<\p{XDigit}> now matches the same characters as C<\p{Hex_Digit}>. This
177 means that in addition to the characters it currently matches,
178 C<[A-Fa-f0-9]>, it will also match the 22 fullwidth equivalents, for
179 example U+FF10: FULLWIDTH DIGIT ZERO.
181 The Numeric type property has been extended to include the Unihan
184 There is a new Perl extension, the 'Present_In', or simply 'In',
185 property. This is an extension of the Unicode Age property, but
186 C<\p{In=5.0}> matches any code point whose usage has been determined
187 I<as of> Unicode version 5.0. The C<\p{Age=5.0}> only matches code points
188 added in I<precisely> version 5.0.
190 A number of properties did not have the correct values for unassigned
191 code points. This is now fixed. The affected properties are
192 Bidi_Class, East_Asian_Width, Joining_Type, Decomposition_Type,
193 Hangul_Syllable_Type, Numeric_Type, and Line_Break.
195 The Default_Ignorable_Code_Point, ID_Continue, and ID_Start properties
196 have been updated to their current Unicode definitions.
198 Certain properties that are supposed to be Unicode internal-only were
199 erroneously exposed by previous Perls. Use of these in regular
200 expressions will now generate, if enabled, a deprecated warning message.
201 The properties are: Other_Alphabetic, Other_Default_Ignorable_Code_Point,
202 Other_Grapheme_Extend, Other_ID_Continue, Other_ID_Start, Other_Lowercase,
203 Other_Math, and Other_Uppercase.
205 An installation can now fairly easily change which Unicode properties
206 Perl understands. As mentioned above, certain properties are by default
207 turned off. These include all the Unihan properties (which should be
208 accessible via the CPAN module Unicode::Unihan) and any deprecated or
209 Unicode internal-only property that Perl has never exposed.
211 The generated files in the C<lib/unicore/To> directory are now more
212 clearly marked as being stable, directly usable by applications.
213 New hash entries in them give the format of the normal entries,
214 which allows for easier machine parsing. Perl can generate files
215 in this directory for any property, though most are suppressed. An
216 installation can choose to change which get written. Instructions
217 are in L<perluniprops>.
219 =head2 Regular Expressions
221 U+0FFFF is now a legal character in regular expressions.
223 =head2 A proper interface for pluggable Method Resolution Orders
225 As of Perl 5.11.0 there is a new interface for plugging and using method
226 resolution orders other than the default (linear depth first search).
227 The C3 method resolution order added in 5.10.0 has been re-implemented as
228 a plugin, without changing its Perl-space interface. See L<perlmroapi> for
231 =head2 The C<overloading> pragma
233 This pragma allows you to lexically disable or enable overloading
234 for some or all operations. (Yuval Kogman)
236 =head2 C<\N> regex escape
238 A new regex escape has been added, C<\N>. It will match any character that
239 is not a newline, independently from the presence or absence of the single
240 line match modifier C</s>. (If C<\N> is followed by an opening brace and
241 by a letter, perl will still assume that a Unicode character name is
242 coming, so compatibility is preserved.) (Rafael Garcia-Suarez)
244 This will break a L<custom charnames translator|charnames/CUSTOM TRANSLATORS>
245 which allows numbers for character names, as C<\N{3}> will now mean to match 3
246 non-newline characters, and not the character whose name is C<3>. (No standard
247 name is a number, so only a custom translator would be affected.)
249 =head2 Implicit strictures
251 Using the C<use VERSION> syntax with a version number greater or equal
252 to 5.11.0 will also lexically enable strictures just like C<use strict>
253 would do (in addition to enabling features.) So, the following:
262 =head2 Parallel tests
264 The core distribution can now run its regression tests in parallel on
265 Unix-like platforms. Instead of running C<make test>, set C<TEST_JOBS> in
266 your environment to the number of tests to run in parallel, and run
267 C<make test_harness>. On a Bourne-like shell, this can be done as
269 TEST_JOBS=3 make test_harness # Run 3 tests in parallel
271 An environment variable is used, rather than parallel make itself, because
272 L<TAP::Harness> needs to be able to schedule individual non-conflicting test
273 scripts itself, and there is no standard interface to C<make> utilities to
274 interact with their job schedulers.
276 Note that currently some test scripts may fail when run in parallel (most
277 notably C<ext/IO/t/io_dir.t>). If necessary run just the failing scripts
278 again sequentially and see if the failures go away.
280 =head2 The C<...> operator
282 A new operator, C<...>, nicknamed the Yada Yada operator, has been added.
283 It is intended to mark placeholder code that is not yet implemented.
284 See L<perlop/"Yada Yada Operator">. (chromatic)
286 =head2 DTrace support
288 Some support for DTrace has been added. See "DTrace support" in F<INSTALL>.
290 =head2 Support for C<configure_requires> in CPAN module metadata
292 Both C<CPAN> and C<CPANPLUS> now support the C<configure_requires> keyword
293 in the F<META.yml> metadata file included in most recent CPAN distributions.
294 This allows distribution authors to specify configuration prerequisites that
295 must be installed before running F<Makefile.PL> or F<Build.PL>.
297 See the documentation for C<ExtUtils::MakeMaker> or C<Module::Build> for more
298 on how to specify C<configure_requires> when creating a distribution for CPAN.
300 =head2 C<each> is now more flexible
302 The C<each> function can now operate on arrays.
304 =head2 Y2038 compliance
306 Perl's core time-related functions are now Y2038 compliant. (With 29
309 =head2 C<$,> flexibility
311 The variable C<$,> may now be tied.
313 =head2 // in where clauses
315 // now behaves like || in when clauses
317 =head2 Enabling warnings from your shell environment
319 You can now set C<-W> from the C<PERL5OPT> environment variable
321 =head2 C<delete local>
323 C<delete local> now allows you to locally delete a hash entry.
325 =head2 New support for Abstract namespace sockets
327 Abstract namespace sockets are Linux-specific socket type that live in
328 AF_UNIX family, slightly abusing it to be able to use arbitrary
329 character arrays as addresses: They start with nul byte and are not
330 terminated by nul byte, but with the length passed to the socket()
333 =head2 New C<package NAME VERSION> syntax
335 This new syntax allows a module author to set the $VERSION of a namespace
336 when the namespace is declared with 'package'. It eliminates the need
337 for C<our $VERSION = ...> and similar constructs. E.g.
339 package Foo::Bar 1.23;
340 # $Foo::Bar::VERSION == 1.23
342 There are several advantages to this:
348 C<$VERSION> is parsed in exactly the same way as C<use NAME VERSION>
352 C<$VERSION> is set at compile time
356 C<$VERSION> is a version object that provides proper overloading of
357 comparision operators so comparing C<$VERSION> to decimal (1.23) or
358 dotted-decimal (v1.2.3) version numbers works correctly.
362 Eliminates C<$VERSION = ...> and C<eval $VERSION> clutter
366 As it requires VERSION to be a numeric literal or v-string
367 literal, it can be statically parsed by toolchain modules
368 without C<eval> the way MM-E<gt>parse_version does for C<$VERSION = ...>
372 It does not break old code with only C<package NAME>, but code that uses
373 C<package NAME VERSION> will need to be restricted to perl 5.12.0 or newer
374 This is analogous to the change to C<open> from two-args to three-args.
375 Users requiring the latest Perl will benefit, and perhaps after several
376 years, it will become a standard practice.
380 However, C<package NAME VERSION> requires a new, 'strict' version
381 number format. See L<"Version number formats"> for details.
383 =head1 Incompatible Changes
385 =head2 Version number formats
387 Acceptable version number formats have been formalized into "strict" and
388 "lax" rules. C<package NAME VERSION> takes a strict version number.
389 C<UNIVERSAL::VERSION> and the L<version> object constructors take lax
390 version numbers. Providing an invalid version will result in a fatal
391 error. The version argument in C<use NAME VERSION> is first parsed as a
392 numeric literal or v-string and then passed to C<UNIVERSAL::VERSION>
393 (and must then pass the "lax" format test).
395 These formats are documented fully in the L<version> module. To a first
396 approximation, a "strict" version number is a positive decimal number
397 (integer or decimal-fraction) without exponentiation or else a
398 dotted-decimal v-string with a leading 'v' character and at least three
399 components. A "lax" version number allows v-strings with fewer than
400 three components or without a leading 'v'. Under "lax" rules, both
401 decimal and dotted-decimal versions may have a trailing "alpha"
402 component separated by an underscore character after a fractional or
403 dotted-decimal component.
405 The L<version> module adds C<version::is_strict> and C<version::is_lax>
406 functions to check a scalar against these rules.
408 =head2 @INC reorganization
410 In @INC, ARCHLIB and PRIVLIB now occur after after the current version's
411 site_perl and vendor_perl.
413 =head2 Switch statement changes
415 The handling of complex expressions by the C<given>/C<when> switch
416 statement has been enhanced. These enhancements are also available in
417 5.10.1 and subsequent 5.10 releases. There are two new cases where
418 C<when> now interprets its argument as a boolean, instead of an
419 expression to be used in a smart match:
421 =head2 flip-flop operators
423 The C<..> and C<...> flip-flop operators are now evaluated in boolean
424 context, following their usual semantics; see L<perlop/"Range Operators">.
426 Note that, as in perl 5.10.0, C<when (1..10)> will not work to test
427 whether a given value is an integer between 1 and 10; you should use
428 C<when ([1..10])> instead (note the array reference).
430 However, contrary to 5.10.0, evaluating the flip-flop operators in boolean
431 context ensures it can now be useful in a C<when()>, notably for
432 implementing bistable conditions, like in:
434 when (/^=begin/ .. /^=end/) {
438 =head2 defined-or operator
440 A compound expression involving the defined-or operator, as in
441 C<when (expr1 // expr2)>, will be treated as boolean if the first
442 expression is boolean. (This just extends the existing rule that applies
443 to the regular or operator, as in C<when (expr1 || expr2)>.)
445 =head2 Smart match changes
447 This section details more changes brought to the semantics to
448 the smart match operator, that naturally also modify the behaviour
449 of the switch statements where smart matching is implicitly used.
450 These changes were also made for the 5.10.1 release, and will remain in
451 subsequent 5.10 releases.
453 =head3 Changes to type-based dispatch
455 The smart match operator C<~~> is no longer commutative. The behaviour of
456 a smart match now depends primarily on the type of its right hand
457 argument. Moreover, its semantics have been adjusted for greater
458 consistency or usefulness in several cases. While the general backwards
459 compatibility is maintained, several changes must be noted:
465 Code references with an empty prototype are no longer treated specially.
466 They are passed an argument like the other code references (even if they
467 choose to ignore it).
471 C<%hash ~~ sub {}> and C<@array ~~ sub {}> now test that the subroutine
472 returns a true value for each key of the hash (or element of the
473 array), instead of passing the whole hash or array as a reference to
478 Due to the commutativity breakage, code references are no longer
479 treated specially when appearing on the left of the C<~~> operator,
480 but like any vulgar scalar.
484 C<undef ~~ %hash> is always false (since C<undef> can't be a key in a
485 hash). No implicit conversion to C<""> is done (as was the case in perl
490 C<$scalar ~~ @array> now always distributes the smart match across the
491 elements of the array. It's true if one element in @array verifies
492 C<$scalar ~~ $element>. This is a generalization of the old behaviour
493 that tested whether the array contained the scalar.
497 The full dispatch table for the smart match operator is given in
498 L<perlsyn/"Smart matching in detail">.
500 =head3 Smart match and overloading
502 According to the rule of dispatch based on the rightmost argument type,
503 when an object overloading C<~~> appears on the right side of the
504 operator, the overload routine will always be called (with a 3rd argument
505 set to a true value, see L<overload>.) However, when the object will
506 appear on the left, the overload routine will be called only when the
507 rightmost argument is a simple scalar. This way, distributivity of smart
508 match across arrays is not broken, as well as the other behaviours with
509 complex types (coderefs, hashes, regexes). Thus, writers of overloading
510 routines for smart match mostly need to worry only with comparing
511 against a scalar, and possibly with stringification overloading; the
512 other common cases will be automatically handled consistently.
514 C<~~> will now refuse to work on objects that do not overload it (in order
515 to avoid relying on the object's underlying structure). (However, if the
516 object overloads the stringification or the numification operators, and
517 if overload fallback is active, it will be used instead, as usual.)
519 =head2 Labels can't be keywords
521 Labels used as targets for the C<goto>, C<last>, C<next> or C<redo>
522 statements cannot be keywords anymore. This restriction will prevent
523 potential confusion between the C<goto LABEL> and C<goto EXPR> syntaxes:
524 for example, a statement like C<goto print> would jump to a label whose
525 name would be the return value of C<print()>, (usually 1), instead of a
526 label named C<print>. Moreover, the other control flow statements
527 would just ignore any keyword passed to them as a label name. Since
528 such labels cannot be defined anymore, this kind of error will be
531 =head2 Other incompatible changes
537 The definitions of a number of Unicode properties have changed to match those
538 of the current Unicode standard. These are listed above under L</Unicode
539 properties>. This could break code that is expecting the old definitions.
543 The boolkeys op moved to the group of hash ops. This breaks binary
548 Filehandles are blessed directly into C<IO::Handle>, as C<FileHandle> is
549 merely a wrapper around C<IO::Handle>.
551 The previous behaviour was to bless Filehandles into L<FileHandle>
552 (an empty proxy class) if it was loaded into memory and otherwise
553 to bless them into C<IO::Handle>.
557 The semantics of C<use feature :5.10*> have changed slightly.
558 See L<"Modules and Pragmata"> for more information.
562 The version control system used for the development of the perl
563 interpreter has been switched from Perforce to git. This is mainly an
564 internal issue that only affects people actively working on the perl core;
565 but it may have minor external visibility, for example in some of details
566 of the output of C<perl -V>. See L<perlrepository> for more information.
570 The internal structure of the C<ext/> directory in the perl source has
571 been reorganised. In general, a module C<Foo::Bar> whose source was
572 stored under F<ext/Foo/Bar/> is now located under F<ext/Foo-Bar/>. Also,
573 nearly all dual-life modules have been moved from F<lib/> to F<ext/>. This
574 is purely a source tarball change, and should make no difference to the
575 compilation or installation of perl, unless you have a very customised build
576 process that explicitly relies on this structure, or which hard-codes the
577 C<nonxs_ext> F<Configure> parameter. Specifically, this change does not by
578 default alter the location of any files in the final installation.
582 As part of the C<Test::Harness> 2.x to 3.x upgrade, the experimental
583 C<Test::Harness::Straps> module has been removed.
584 See L</"Updated Modules"> for more details.
588 As part of the C<ExtUtils::MakeMaker> upgrade, the
589 C<ExtUtils::MakeMaker::bytes> and C<ExtUtils::MakeMaker::vmsish> modules
590 have been removed from this distribution.
594 C<Module::CoreList> no longer contains the C<%:patchlevel> hash.
598 This one is actually a change introduced in 5.10.0, but it was missed
599 from that release's perldelta, so it is mentioned here instead.
601 A bugfix related to the handling of the C</m> modifier and C<qr> resulted
602 in a change of behaviour between 5.8.x and 5.10.0:
604 # matches in 5.8.x, doesn't match in 5.10.0
605 $re = qr/^bar/; "foo\nbar" =~ /$re/m;
609 C<length undef> now returns undef.
613 Unsupported private C API functions are now declared "static" to prevent
614 leakage to Perl's public API.
618 To support the bootstrapping process, F<miniperl> no longer builds with
619 UTF-8 support in the regexp engine.
621 This allows a build to complete with PERL_UNICODE set and a UTF-8 locale.
622 Without this there's a bootstrapping problem, as miniperl can't load the UTF-8
623 components of the regexp engine, because they're not yet built.
627 F<miniperl>'s @INC is now restricted to just C<-I...>, the split of
628 C<$ENV{PERL5LIB}>, and "C<.>"
632 A space or a newline is now required after a C<"#line XXX"> directive.
636 Tied filehandles now have an additional method EOF which provides the EOF type
640 To better match all other flow control statements, C<foreach> may no
641 longer be used as an attribute.
647 From time to time, Perl's developers find it necessary to deprecate
648 features or modules we've previously shipped as part of the core
649 distribution. We are well aware of the pain and frustration that a
650 backwards-incompatible change to Perl can cause for developers building
651 or maintaining software in Perl. You can be sure that when we deprecate
652 a functionality or syntax, it isn't a choice we make lightly. Sometimes,
653 we choose to deprecate functionality or syntax because it was found to
654 be poorly designed or implemented. Sometimes, this is because they're
655 holding back other features or causing performance problems. Sometimes,
656 the reasons are more complex. Wherever possible, we try to keep deprecated
657 functionality available to developers in its previous form for at least
658 one major release. So long as a deprecated feature isn't actively
659 disrupting our ability to maintain and extend Perl, we'll try to leave
660 it in place as long as possible.
662 The following items are now deprecated.
666 =item Use of C<:=> to mean an empty attribute list is now deprecated.
668 An accident of Perl's parser meant that these constructions were all
675 with the C<:> being treated as the start of an attribute list, which
676 ends before the C<=>. As whitespace is not significant here, all are
677 parsed as an empty attribute list, hence all the above are equivalent
678 to, and better written as
682 because no attribute processing is done for an empty list.
684 As is, this meant that C<:=> cannot be used as a new token, without
685 silently changing the meaning of existing code. Hence that particular
686 form is now deprecated, and will become a syntax error. If it is
687 absolutely necessary to have empty attribute lists (for example,
688 because of a code generator) then avoid the warning by adding a space
691 =item C<< UNIVERSAL->import() >>
693 The method C<< UNIVERSAL->import() >> is now deprecated. Attempting to
694 pass import arguments to a C<use UNIVERSAL> statement will result in a
697 =item Use of "goto" to jump into a construct is deprecated
699 Using C<goto> to jump from an outer scope into an inner scope is now
700 deprecated. This rare use case was causing problems in the
701 implementation of scopes.
703 =item Deprecated Modules
705 The following modules will be removed from the core distribution in a future
706 release, and should be installed from CPAN instead. Distributions on CPAN
707 which require these should add them to their prerequisites. The core versions
708 of these modules warnings will issue a deprecation warning.
714 =item L<Pod::Plainer>
720 Switch is buggy and should be avoided. See L<perlsyn/"Switch
721 statements"> for its replacement.
727 C<suidperl> has been removed. It used to provide a mechanism to
728 emulate setuid permission bits on systems that don't support it properly.
730 =item Assignment to $[
734 Remove attrs, which has been deprecated since 1999-10-02.
736 =item Use of the attribute :locked on subroutines.
738 =item Use of "locked" with the attributes pragma.
740 =item Use of "unique" with the attributes pragma.
742 =item Numerous Perl 4-era libraries:
744 F<termcap.pl>, F<tainted.pl>, F<stat.pl>, F<shellwords.pl>, F<pwd.pl>,
745 F<open3.pl>, F<open2.pl>, F<newgetopt.pl>, F<look.pl>, F<find.pl>,
746 F<finddepth.pl>, F<importenv.pl>, F<hostname.pl>, F<getopts.pl>,
747 F<getopt.pl>, F<getcwd.pl>, F<flush.pl>, F<fastcwd.pl>, F<exceptions.pl>,
748 F<ctime.pl>, F<complete.pl>, F<cacheout.pl>, F<bigrat.pl>, F<bigint.pl>,
749 F<bigfloat.pl>, F<assert.pl>, F<abbrev.pl>, F<dotsh.pl>, and
750 F<timelocal.pl> are all now deprecated. Using them will incur a warning.
754 =head1 Modules and Pragmata
756 =head2 Dual-lifed modules moved
758 Dual-lifed modules maintained primarily in the Perl core now live in dist/.
759 Dual-lifed modules maintained primarily on CPAN now live in cpan/
761 In previous releases of Perl, it was customary to enumerate all module
762 changes in this section of the C<perldelta> file. From 5.11.0 forward
763 only notable updates (such as new or deprecated modules ) will be listed
764 in this section. For a complete reference to the versions of modules
765 shipped in a given release of perl, please see L<Module::CoreList>.
767 =head2 New Modules and Pragmata
775 This is a new lexically-scoped alternative for the C<Fatal> module.
776 The bundled version is 2.06_01. Note that in this release, using a string
777 eval when C<autodie> is in effect can cause the autodie behaviour to leak
778 into the surrounding scope. See L<autodie/"BUGS"> for more details.
782 C<Compress::Raw::Bzip2>
784 This has been added to the core (version 2.020).
790 This pragma establishes an ISA relationship with base classes at compile
791 time. It provides the key feature of C<base> without further unwanted
798 This has been added to the core (version 1.39).
802 =head2 Pragmata Changes
810 See L</"The C<overloading> pragma"> above.
816 The C<attrs> pragma has been removed. It had been marked as deprecated since
823 The Unicode F<NameAliases.txt> database file has been added. This has the
824 effect of adding some extra C<\N> character names that formerly wouldn't
825 have been recognised; for example, C<"\N{LATIN CAPITAL LETTER GHA}">.
831 The meaning of the C<:5.10> and C<:5.10.X> feature bundles has
832 changed slightly. The last component, if any (i.e. C<X>) is simply ignored.
833 This is predicated on the assumption that new features will not, in
834 general, be added to maintenance releases. So C<:5.10> and C<:5.10.X>
835 have identical effect. This is a change to the behaviour documented for
842 Upgraded from version 1.00 to 1.01. Performance for single inheritance is 40%
843 faster - see L</"Performance Enhancements"> below.
845 C<mro> is now implemented as an XS extension. The documented interface has not
846 changed. Code relying on the implementation detail that some C<mro::>
847 methods happened to be available at all times gets to "keep both pieces".
853 Supports %.0f formatting internally.
859 Allow overloading of 'qr'.
865 Upgraded from version 1.19 to 1.20.
871 This pragma no longer suppresses C<Use of uninitialized value in range
872 (or flip)> warnings. [perl #71204]
878 Upgraded from 1.13 to 1.14. Added the C<unicode_strings> feature:
880 use feature "unicode_strings";
882 This pragma turns on Unicode semantics for the case-changing operations
883 (C<uc>, C<lc>, C<ucfirst>, C<lcfirst>) on strings that don't have the
884 internal UTF-8 flag set, but that contain single-byte characters between
891 Upgraded from version 1.74 to 1.75.
897 Upgraded from version 0.02 to 0.03.
899 This version introduces the C<stash_name> method to allow subclasses of
900 C<less> to pick where in %^H to store their stash.
906 Upgraded from version 0.77 to 0.81.
908 This version adds support for L</Version number formats> as described earlier
909 in this document and in its own documentation.
915 Upgraded from 1.07 to 1.09.
917 Added new C<warnings::fatal_enabled()> function.
918 This version adds the C<illegalproto> warning category. See also L</New or
919 Changed Diagnostics> for this change.
924 =head2 Updated Modules
928 =item XXX TODO RECALCULATE THIS VS 5.10.0
932 =head2 Removed Modules and Pragmata
940 Removed from the Perl core. Prior version was 'undef'.
946 =head2 New Documentation
954 This contains instructions on how to build perl for the Haiku platform.
960 This describes the new interface for pluggable Method Resolution Orders.
966 This document, by Richard Foley, provides an introduction to the use of
967 performance and optimization techniques which can be used with particular
968 reference to perl programs.
974 This describes how to access the perl source using the I<git> version
979 L<perlpolicy> extends the "Social contract about contributed modules" into
980 the beginnings of a document on Perl porting policies.
984 =head2 Changes to Existing Documentation
986 The various large F<Changes*> files (which listed every change made to perl
987 over the last 18 years) have been removed, and replaced by a small file,
988 also called F<Changes>, which just explains how that same information may
989 be extracted from the git version control system.
991 The file F<Porting/patching.pod> has been deleted, as it mainly described
992 interacting with the old Perforce-based repository, which is now obsolete.
993 Information still relevant has been moved to L<perlrepository>.
995 L<perlapi>, L<perlintern>, L<perlmodlib> and L<perltoc> are now all
996 generated at build time, rather than being shipped as part of the release.
1002 Documented -X overloading.
1006 Documented that C<when()> treats specially most of the filetest operators
1010 Documented C<when> as a syntax modifier
1014 Eliminated "Old Perl threads tutorial", which described 5005 threads.
1016 F<pod/perlthrtut.pod> is the same material reworked for ithreads.
1020 Correct previous documentation: v-strings are not deprecated
1022 With version objects, we need them to use MODULE VERSION syntax. This
1023 patch removes the deprecation notice.
1027 Added security contact information to L<perlsec>
1029 A significant fraction of the core documentation has been updated to clarify
1030 the behavior of Perl's Unicode handling.
1032 Much of the remaining core documentation has been reviewed and edited
1033 for clarity, consistent use of language, and to fix the spelling of Tom
1034 Christiansen's name.
1036 The Pod specification (L<perlpodspec>) has been updated to bring the
1037 specification in line with modern usage already supported by most Pod
1038 systems. A parameter string may now follow the format name in a
1039 "begin/end" region. Links to URIs with a text description are now
1040 allowed. The usage of C<LE<lt>"section"E<gt>> has been marked as
1043 L<if.pm|if> has been documented in L<perlfunc/use> as a means to get
1044 conditional loading of modules despite the implicit BEGIN block around
1049 The documentation for C<$1> in perlvar.pod has been clarified.
1053 =head1 Performance Enhancements
1059 A new internal cache means that C<isa()> will often be faster.
1063 The implementation of C<C3> Method Resolution Order has been optimised -
1064 linearisation for classes with single inheritance is 40% faster. Performance
1065 for multiple inheritance is unchanged.
1069 Under C<use locale>, the locale-relevant information is now cached on
1070 read-only values, such as the list returned by C<keys %hash>. This makes
1071 operations such as C<sort keys %hash> in the scope of C<use locale> much
1076 Empty C<DESTROY> methods are no longer called.
1080 Faster C<Perl_sv_utf8_upgrade()>
1084 Speed up C<keys> on empty hash
1088 C<if (%foo)> has been optimized to be faster than C<if (keys %foo)>
1092 Reversing an array to itself (as in C<@a = reverse @a>) in void context
1093 now happens in-place and is several orders of magnitude faster than it
1094 used to be. It will also preserve non-existent elements whenever
1095 possible, i.e. for non magical arrays or tied arrays with C<EXISTS> and
1100 =head1 Installation and Configuration Improvements
1102 =head2 F<ext/> reorganisation
1104 The layout of directories in F<ext> has been revised. Specifically, all
1105 extensions are now flat, and at the top level, with C</> in pathnames
1106 replaced by C<->, so that F<ext/Data/Dumper/> is now F<ext/Data-Dumper/>,
1107 etc. The names of the extensions as specified to F<Configure>, and as
1108 reported by C<%Config::Config> under the keys C<dynamic_ext>,
1109 C<known_extensions>, C<nonxs_ext> and C<static_ext> have not changed, and
1110 still use C</>. Hence this change will not have any affect once perl is
1111 installed. C<Safe> has been split out from being part of C<Opcode>, and
1112 C<mro> is now an extension in its own right.
1114 Nearly all dual-life modules have been moved from F<lib> to F<ext>, and will
1115 now appear as known C<nonxs_ext>. This will made no difference to the
1116 structure of an installed perl, nor will the modules installed differ,
1117 unless you run F<Configure> with options to specify an exact list of
1118 extensions to build. In this case, you will rapidly become aware that you
1119 need to add to your list, because various modules needed to complete the
1120 build, such as C<ExtUtils::ParseXS>, have now become extensions, and
1121 without them the build will fail well before it attempts to run the
1124 =head2 Configuration improvements
1126 If C<vendorlib> and C<vendorarch> are the same, then they are only added to
1129 C<$Config{usedevel}> and the C-level C<PERL_USE_DEVEL> are now defined if
1130 perl is built with C<-Dusedevel>.
1132 F<Configure> will enable use of C<-fstack-protector>, to provide protection
1133 against stack-smashing attacks, if the compiler supports it.
1135 F<Configure> will now determine the correct prototypes for re-entrant
1136 functions and for C<gconvert> if you are using a C++ compiler rather
1139 On Unix, if you build from a tree containing a git repository, the
1140 configuration process will note the commit hash you have checked out, for
1141 display in the output of C<perl -v> and C<perl -V>. Unpushed local commits
1142 are automatically added to the list of local patches displayed by
1145 USE_ATTRIBUTES_FOR_PERLIO is now reported in the compile-time options
1146 listed by the C<-V> switch.
1148 =head2 Compilation improvements
1150 As part of the flattening of F<ext>, all extensions on all platforms are
1151 built by F<make_ext.pl>. This replaces the Unix-specific
1152 F<ext/util/make_ext>, VMS-specific F<make_ext.com> and Win32-specific
1153 F<win32/buildext.pl>.
1155 =head1 Changed Internals
1161 C<Perl_pmflag> has been removed from the public API. Calling it now
1162 generates a deprecation warning, and it will be removed in a future
1163 release. Although listed as part of the API, it was never documented,
1164 and only ever used in F<toke.c>, and prior to 5.10, F<regcomp.c>. In
1165 core, it has been replaced by a static function.
1169 Perl_magic_setmglob now knows about globs, fixing RT #71254.
1173 TODO: C<SVt_RV> is gone. RVs are now stored in IVs
1177 TODO: REGEXPs are first class
1181 TODO: OOK is reworked, such that an OOKed scalar is PV not PVIV
1185 The J.R.R. Tolkien quotes at the head of C source file have been checked and
1186 proper citations added, thanks to a patch from Tom Christiansen.
1190 C<Perl_vcroak()> now accepts a null first argument. In addition, a full audit
1191 was made of the "not NULL" compiler annotations, and those for several
1192 other internal functions were corrected.
1196 New macros C<dSAVEDERRNO>, C<dSAVE_ERRNO>, C<SAVE_ERRNO>, C<RESTORE_ERRNO>
1197 have been added to formalise the temporary saving of the C<errno>
1202 The function C<Perl_sv_insert_flags> has been added to augment
1207 The function C<Perl_newSV_type(type)> has been added, equivalent to
1208 C<Perl_newSV()> followed by C<Perl_sv_upgrade(type)>.
1212 The function C<Perl_newSVpvn_flags()> has been added, equivalent to
1213 C<Perl_newSVpvn()> and then performing the action relevant to the flag.
1215 Two flag bits are currently supported.
1223 This will call C<SvUTF8_on()> for you. (Note that this does not convert an
1224 sequence of ISO 8859-1 characters to UTF-8). A wrapper, C<newSVpvn_utf8()>
1225 is available for this.
1231 Call C<Perl_sv_2mortal()> on the new SV.
1235 There is also a wrapper that takes constant strings, C<newSVpvs_flags()>.
1239 The function C<Perl_croak_xs_usage> has been added as a wrapper to
1244 The functions C<PerlIO_find_layer> and C<PerlIO_list_alloc> are now
1249 C<PL_na> has been exterminated from the core code, replaced by local STRLEN
1250 temporaries, or C<*_nolen()> calls. Either approach is faster than C<PL_na>,
1251 which is a pointer dereference into the interpreter structure under ithreads,
1252 and a global variable otherwise.
1256 C<Perl_mg_free()> used to leave freed memory accessible via C<SvMAGIC()> on
1257 the scalar. It now updates the linked list to remove each piece of magic
1262 Under ithreads, the regex in C<PL_reg_curpm> is now reference counted. This
1263 eliminates a lot of hackish workarounds to cope with it not being reference
1268 C<Perl_mg_magical()> would sometimes incorrectly turn on C<SvRMAGICAL()>.
1269 This has been fixed.
1273 The I<public> IV and NV flags are now not set if the string value has
1274 trailing "garbage". This behaviour is consistent with not setting the
1275 public IV or NV flags if the value is out of range for the type.
1279 SV allocation tracing has been added to the diagnostics enabled by C<-Dm>.
1280 The tracing can alternatively output via the C<PERL_MEM_LOG> mechanism, if
1281 that was enabled when the F<perl> binary was compiled.
1285 Smartmatch resolution tracing has been added as a new diagnostic. Use C<-DM> to
1290 A new debugging flag C<-DB> now dumps subroutine definitions, leaving
1291 C<-Dx> for its original purpose of dumping syntax trees.
1295 Uses of C<Nullav>, C<Nullcv>, C<Nullhv>, C<Nullop>, C<Nullsv> etc have been
1296 replaced by C<NULL> in the core code, and non-dual-life modules, as C<NULL>
1297 is clearer to those unfamiliar with the core code.
1301 A macro C<MUTABLE_PTR(p)> has been added, which on (non-pedantic) gcc will
1302 not cast away C<const>, returning a C<void *>. Macros C<MUTABLE_SV(av)>,
1303 C<MUTABLE_SV(cv)> etc build on this, casting to C<AV *> etc without
1304 casting away C<const>. This allows proper compile-time auditing of
1305 C<const> correctness in the core, and helped picked up some errors (now
1310 Macros C<mPUSHs()> and C<mXPUSHs()> have been added, for pushing SVs on the
1311 stack and mortalizing them.
1315 Use of the private structure C<mro_meta> has changed slightly. Nothing
1316 outside the core should be accessing this directly anyway.
1320 A new tool, F<Porting/expand-macro.pl> has been added, that allows you
1321 to view how a C preprocessor macro would be expanded when compiled.
1322 This is handy when trying to decode the macro hell that is the perl
1331 Many modules updated from CPAN incorporate new tests.
1332 Several tests that have the potential to hang forever if they fail now
1333 incorporate a "watchdog" functionality that will kill them after a timeout,
1334 which helps ensure that C<make test> and C<make test_harness> run to
1335 completion automatically. (Jerry Hedden).
1337 Some core-specific tests have been added:
1343 Significant cleanups to core tests to ensure that language and
1344 interpreter features are not used before they're tested.
1348 C<make test_porting> now runs a number of important pre-commit checks
1349 which might be of use to anyone working on the Perl core.
1353 F<t/porting/podcheck.t> automatically checks the well-formedness of
1354 POD found in all .pl, .pm and .pod files in the F<MANIFEST>, other than in
1355 dual-lifed modules which are primarily maintained outside the Perl core.
1359 F<t/porting/manifest.t> now tests that all files listed in MANIFEST are present.
1363 F<t/op/while_readdir.t>
1365 Test that a bare readdir in while loop sets $_.
1369 F<t/comp/retainedlines.t>
1371 Check that the debugger can retain source lines from C<eval>.
1375 F<t/io/perlio_fail.t>
1377 Check that bad layers fail.
1381 F<t/io/perlio_leaks.t>
1383 Check that PerlIO layers are not leaking.
1387 F<t/io/perlio_open.t>
1389 Check that certain special forms of open work.
1395 General PerlIO tests.
1401 Check that there is no unexpected interaction between the internal types
1402 C<PVBM> and C<PVGV>.
1406 F<t/mro/package_aliases.t>
1408 Check that mro works properly in the presence of aliased packages.
1414 Tests for C<dbmopen> and C<dbmclose>.
1420 Tests for the interaction of C<index> and threads.
1426 Tests for the interaction of esoteric patterns and threads.
1432 Test that C<qr> doesn't leak.
1436 F<t/op/reg_email_thr.t>
1438 Tests for the interaction of regex recursion and threads.
1442 F<t/op/regexp_qr_embed_thr.t>
1444 Tests for the interaction of patterns with embedded C<qr//> and threads.
1448 F<t/op/regexp_unicode_prop.t>
1450 Tests for Unicode properties in regular expressions.
1454 F<t/op/regexp_unicode_prop_thr.t>
1456 Tests for the interaction of Unicode properties and threads.
1460 F<t/op/reg_nc_tie.t>
1462 Test the tied methods of C<Tie::Hash::NamedCapture>.
1466 F<t/op/reg_posixcc.t>
1468 Check that POSIX character classes behave consistently.
1474 Check that exportable C<re> functions in F<universal.c> work.
1478 F<t/op/setpgrpstack.t>
1480 Check that C<setpgrp> works.
1484 F<t/op/substr_thr.t>
1486 Tests for the interaction of C<substr> and threads.
1492 Check that upgrading and assigning scalars works.
1498 Check that Unicode in the lexer works.
1504 Check that Unicode and C<tie> work.
1508 F<t/comp/final_line_num.t>
1510 See if line numbers are correct at EOF
1514 F<t/comp/form_scope.t>
1516 See if format scoping works
1520 F<t/comp/line_debug.t>
1522 See if C<< @{"_<$file"} >> works
1526 F<t/op/filetest_t.t>
1528 See if -t file test works
1540 Tests malfunctions of utf8 cache
1546 Test unicode \p{} regex constructs
1550 =head2 Testing improvements
1556 It's now possible to override C<PERL5OPT> and friends in F<t/TEST>
1561 =head1 New or Changed Diagnostics
1563 Several new diagnostics, see L<perldiag> for details.
1569 C<Bad plugin affecting keyword '%s'>
1573 C<gmtime(%.0f) too large>
1577 C<Lexing code attempted to stuff non-Latin-1 character into Latin-1 input>
1581 C<Lexing code internal error (%s)>
1585 C<localtime(%.0f) too large>
1589 C<Overloaded dereference did not return a reference>
1593 C<Overloaded qr did not return a REGEXP>
1597 C<Perl_pmflag() is deprecated, and will be removed from the XS API>
1601 New warning category C<illegalproto>
1605 Illegal character in prototype for %s : %s
1606 Prototype after '%c' for %s : %s
1608 have been moved from the C<syntax> top-level warnings category into a new
1609 first-level category, C<illegalproto>. These two warnings are currently the
1610 only ones emitted during parsing of an invalid/illegal prototype, so one
1613 no warnings 'illegalproto';
1615 to suppress only those, but not other syntax-related warnings. Warnings where
1616 prototypes are changed, ignored, or not met are still in the C<prototype>
1617 category as before. (Matt S. Trout)
1621 lvalue attribute ignored after the subroutine has been defined
1623 This new warning is issued when one attempts to mark a subroutine as
1624 lvalue after it has been defined.
1628 warn if C<++> or C<--> are unable to change the value because it's
1629 beyond the limit of representation
1631 This uses a new warnings category: "imprecision".
1635 C<lc>, C<uc>, C<lcfirst>, and C<ucfirst> warn when passed undef.
1639 Show constant in "Useless use of a constant in void context"
1643 Make the new warning report undef constants as undef
1647 Add a new warning, "Prototype after '%s'"
1651 Tweak the "Illegal character in prototype" warning so it's more precise
1652 when reporting illegal characters after _
1656 Correct the unintended interpolation of C<$\> in regex
1660 Make overflow warnings in C<gmtime> and C<localtime> only occur when
1661 warnings are enabled
1665 Improve mro merging error messages.
1667 They are now very similar to those produced by Algorithm::C3.
1671 Amelioration of the error message "Unrecognized character %s in column %d"
1673 Changes the error message to "Unrecognized character %s; marked by E<lt>--
1674 HERE after %sE<lt>-- HERE near column %d". This should make it a little
1675 simpler to spot and correct the suspicious character.
1679 Explicitely point to C<$.> when it causes an uninitialized warning for
1680 ranges in scalar context
1684 C<split> now warns when called in void context
1688 C<printf>-style functions called with too few arguments will now issue the
1689 warning C<"Missing argument in %s"> [perl #71000]
1693 C<panic: sv_chop %s>
1695 This new fatal error occurs when the C routine C<Perl_sv_chop()> was
1696 passed a position that is not within the scalar's string buffer. This
1697 could be caused by buggy XS code, and at this point recovery is not
1702 C<Deep recursion on subroutine "%s">
1704 It is now possible to change the depth threshold for this warning from the
1705 default of 100, by recompiling the F<perl> binary, setting the C
1706 pre-processor macro C<PERL_SUB_DEPTH_WARN> to the desired value.
1710 Perl now properly returns a syntax error instead of segfaulting
1711 if C<each>, C<keys>, or C<values> is used without an argument.
1715 C<tell()> now fails properly if called without an argument and when no
1716 previous file was read.
1718 C<tell()> now returns C<-1>, and sets errno to C<EBADF>, thus restoring
1719 the 5.8.x behaviour.
1723 C<overload> no longer implicitly unsets fallback on repeated 'use
1728 POSIX::strftime() can now handle Unicode characters in the format string.
1732 The Windows select() implementation now supports all empty C<fd_set>s
1737 The "syntax" category was removed from 5 warnings that should only be in
1742 Three fatal C<pack>/C<unpack> error messages have been normalized to
1747 "Unicode character is illegal" has been rephrased to be more accurate
1749 It now reads C<Unicode non-character is illegal in interchange> and the
1750 perldiag documentation has been expanded a bit.
1754 Perl now defaults to issuing a warning if a deprecated language feature
1757 To disable this feature in a given lexical scope, you should use C<no
1758 warnings 'deprecated';> For information about which language features
1759 are deprecated and explanations of various deprecation warnings, please
1764 The following diagnostics have been removed:
1774 C<Can't locate package %s for the parents of %s>
1776 This warning has been removed. In general, it only got produced in
1777 conjunction with other warnings, and removing it allowed an ISA lookup
1778 optimisation to be added.
1782 C<v-string in use/require is non-portable>
1786 =head1 Utility Changes
1794 Now looks in C<include-fixed> too, which is a recent addition to gcc's
1801 No longer incorrectly treats enum values like macros (Daniel Burr).
1803 Now handles C++ style constants (C<//>) properly in enums. (A patch from
1804 Rainer Weikusat was used; Daniel Burr also proposed a similar fix).
1810 C<LVALUE> subroutines now work under the debugger.
1812 The debugger now correctly handles proxy constant subroutines, and
1819 F<perlbug> now uses C<%Module::CoreList::bug_tracker> to print out upstream bug
1822 Where the user names a module that their bug report is about, and we know the
1823 URL for its upstream bug tracker, provide a message to the user explaining
1824 that the core copies the CPAN version directly, and provide the URL for
1825 reporting the bug directly to upstream.
1831 Perl 5.11.0 added a new utility F<perlthanks>, which is a variant of
1832 F<perlbug>, but for sending non-bug-reports to the authors and maintainers
1833 of Perl. Getting nothing but bug reports can become a bit demoralising:
1834 we'll see if this changes things.
1840 No longer reports "Message sent" when it hasn't actually sent the message
1846 Fixed bugs with the match() operator in list context, remove mention of
1851 =head1 Selected Bug Fixes
1857 Ensure that pp_qr returns a new regexp SV each time. Resolves RT #69852.
1859 Instead of returning a(nother) reference to the (pre-compiled) regexp in the
1860 optree, use reg_temp_copy() to create a copy of it, and return a reference to
1861 that. This resolves issues about Regexp::DESTROY not being called in a timely
1862 fashion (the original bug tracked by RT #69852), as well as bugs related to
1863 blessing regexps, and of assigning to regexps, as described in correspondence
1864 added to the ticket.
1866 It transpires that we also need to undo the SvPVX() sharing when ithreads
1867 cloning a Regexp SV, because mother_re is set to NULL, instead of a cloned
1868 copy of the mother_re. This change might fix bugs with regexps and threads in
1869 certain other situations, but as yet neither tests nor bug reports have
1870 indicated any problems, so it might not actually be an edge case that it's
1875 Several compilation errors and segfaults when perl was built with C<-Dmad> were fixed.
1879 Fixes for lexer API changes in 5.11.2 which broke NYTProf's savesrc option.
1883 C<-t> should only return TRUE for file handles connected to a TTY
1885 The Microsoft C version of C<isatty()> returns TRUE for all
1886 character mode devices, including the F</dev/null>-style "nul"
1887 device and printers like "lpt1".
1891 Fixed a regression caused by commit fafafbaf which caused a panic during
1892 parameter passing [perl #70171]
1896 On systems which in-place edits without backup files, -i'*' now works as
1897 the documentation says it does [perl #70802]
1901 Saving and restoring magic flags no longer loses readonly flag.
1905 The malformed syntax C<grep EXPR LIST> (note the missing comma) no longer
1906 causes abrupt and total failure.
1910 Regular expressions compiled with C<qr{}> literals properly set C<$'> when
1915 Using named subroutines with C<sort> should no longer lead to bus errors [perl
1920 Numerous bugfixes catch small issues caused by the recently-added Lexer API.
1924 Smart match against C<@_> sometimes gave false negatives. [perl #71078]
1928 C<$@> may now be assigned a read-only value (without error or busting
1933 C<sort> called recursively from within an active comparison subroutine no
1934 longer causes a bus error if run multiple times. [perl #71076]
1938 Tie::Hash::NamedCapture::* will not abort if passed bad input (RT #71828)
1942 @_ and $_ no longer leak under threads (RT #34342 and #41138, also
1947 C<-I> on shebang line now adds directories in front of @INC
1948 as documented, and as does C<-I> when specified on the command-line.
1952 C<kill> is now fatal when called on non-numeric process identifiers.
1953 Previously, an C<undef> process identifier would be interpreted as a
1954 request to kill process 0, which would terminate the current process
1955 group on POSIX systems. Since process identifiers are always integers,
1956 killing a non-numeric process is now fatal.
1960 5.10.0 inadvertently disabled an optimisation, which caused a measurable
1961 performance drop in list assignment, such as is often used to assign
1962 function parameters from C<@_>. The optimisation has been re-instated, and
1963 the performance regression fixed. (This fix is also present in 5.10.1)
1967 Fixed memory leak on C<while (1) { map 1, 1 }> [RT #53038].
1971 Some potential coredumps in PerlIO fixed [RT #57322,54828].
1975 The debugger now works with lvalue subroutines.
1979 The debugger's C<m> command was broken on modules that defined constants
1984 C<crypt> and string complement could return tainted values for untainted
1985 arguments [RT #59998].
1989 The C<-i>I<.suffix> command-line switch now recreates the file using
1990 restricted permissions, before changing its mode to match the original
1991 file. This eliminates a potential race condition [RT #60904].
1995 On some Unix systems, the value in C<$?> would not have the top bit set
1996 (C<$? & 128>) even if the child core dumped.
2000 Under some circumstances, C<$^R> could incorrectly become undefined
2005 In the XS API, various hash functions, when passed a pre-computed hash where
2006 the key is UTF-8, might result in an incorrect lookup.
2010 XS code including F<XSUB.h> before F<perl.h> gave a compile-time error
2015 C<< $object-E<gt>isa('Foo') >> would report false if the package C<Foo> didn't
2016 exist, even if the object's C<@ISA> contained C<Foo>.
2020 Various bugs in the new-to 5.10.0 mro code, triggered by manipulating
2021 C<@ISA>, have been found and fixed.
2025 Bitwise operations on references could crash the interpreter, e.g.
2026 C<$x=\$y; $x |= "foo"> [RT #54956].
2030 Patterns including alternation might be sensitive to the internal UTF-8
2031 representation, e.g.
2033 my $byte = chr(192);
2034 my $utf8 = chr(192); utf8::upgrade($utf8);
2035 $utf8 =~ /$byte|X}/i; # failed in 5.10.0
2039 Within UTF8-encoded Perl source files (i.e. where C<use utf8> is in
2040 effect), double-quoted literal strings could be corrupted where a C<\xNN>,
2041 C<\0NNN> or C<\N{}> is followed by a literal character with ordinal value
2042 greater than 255 [RT #59908].
2046 C<B::Deparse> failed to correctly deparse various constructs:
2047 C<readpipe STRING> [RT #62428], C<CORE::require(STRING)> [RT #62488],
2048 C<sub foo(_)> [RT #62484].
2052 Using C<setpgrp> with no arguments could corrupt the perl stack.
2056 The block form of C<eval> is now specifically trappable by C<Safe> and
2057 C<ops>. Previously it was erroneously treated like string C<eval>.
2061 In 5.10.0, the two characters C<[~> were sometimes parsed as the smart
2062 match operator (C<~~>) [RT #63854].
2066 In 5.10.0, the C<*> quantifier in patterns was sometimes treated as
2067 C<{0,32767}> [RT #60034, #60464]. For example, this match would fail:
2069 ("ab" x 32768) =~ /^(ab)*$/
2073 C<shmget> was limited to a 32 bit segment size on a 64 bit OS [RT #63924].
2077 Using C<next> or C<last> to exit a C<given> block no longer produces a
2078 spurious warning like the following:
2080 Exiting given via last at foo.pl line 123
2084 On Windows, C<'.\foo'> and C<'..\foo'> were treated differently than
2085 C<'./foo'> and C<'../foo'> by C<do> and C<require> [RT #63492].
2089 Assigning a format to a glob could corrupt the format; e.g.:
2091 *bar=*foo{FORMAT}; # foo format now bad
2095 Attempting to coerce a typeglob to a string or number could cause an
2096 assertion failure. The correct error message is now generated,
2097 C<Can't coerce GLOB to I<$type>>.
2101 Under C<use filetest 'access'>, C<-x> was using the wrong access mode. This
2102 has been fixed [RT #49003].
2106 C<length> on a tied scalar that returned a Unicode value would not be
2107 correct the first time. This has been fixed.
2111 Using an array C<tie> inside in array C<tie> could SEGV. This has been
2116 A race condition inside C<PerlIOStdio_close()> has been identified and
2117 fixed. This used to cause various threading issues, including SEGVs.
2121 In C<unpack>, the use of C<()> groups in scalar context was internally
2122 placing a list on the interpreter's stack, which manifested in various
2123 ways, including SEGVs. This is now fixed [RT #50256].
2127 Magic was called twice in C<substr>, C<\&$x>, C<tie $x, $m> and C<chop>.
2128 These have all been fixed.
2132 A 5.10.0 optimisation to clear the temporary stack within the implicit
2133 loop of C<s///ge> has been reverted, as it turned out to be the cause of
2134 obscure bugs in seemingly unrelated parts of the interpreter [commit
2139 The line numbers for warnings inside C<elsif> are now correct.
2143 The C<..> operator now works correctly with ranges whose ends are at or
2144 close to the values of the smallest and largest integers.
2148 C<binmode STDIN, ':raw'> could lead to segmentation faults on some platforms.
2149 This has been fixed [RT #54828].
2153 An off-by-one error meant that C<index $str, ...> was effectively being
2154 executed as C<index "$str\0", ...>. This has been fixed [RT #53746].
2158 Various leaks associated with named captures in regexes have been fixed
2163 A weak reference to a hash would leak. This was affecting C<DBI>
2168 Using (?|) in a regex could cause a segfault [RT #59734].
2172 Use of a UTF-8 C<tr//> within a closure could cause a segfault [RT #61520].
2176 Calling C<Perl_sv_chop()> or otherwise upgrading an SV could result in an
2177 unaligned 64-bit access on the SPARC architecture [RT #60574].
2181 In the 5.10.0 release, C<inc_version_list> would incorrectly list
2182 C<5.10.*> after C<5.8.*>; this affected the C<@INC> search order
2187 In 5.10.0, C<pack "a*", $tainted_value> returned a non-tainted value
2192 In 5.10.0, C<printf> and C<sprintf> could produce the fatal error
2193 C<panic: utf8_mg_pos_cache_update> when printing UTF-8 strings
2198 In the 5.10.0 release, a dynamically created C<AUTOLOAD> method might be
2199 missed (method cache issue) [RT #60220,60232].
2203 In the 5.10.0 release, a combination of C<use feature> and C<//ee> could
2204 cause a memory leak [RT #63110].
2208 C<-C> on the shebang (C<#!>) line is once more permitted if it is also
2209 specified on the command line. C<-C> on the shebang line used to be a
2210 silent no-op I<if> it was not also on the command line, so perl 5.10.0
2211 disallowed it, which broke some scripts. Now perl checks whether it is
2212 also on the command line and only dies if it is not [RT #67880].
2216 In 5.10.0, certain types of re-entrant regular expression could crash,
2217 or cause the following assertion failure [RT #60508]:
2219 Assertion rx->sublen >= (s - rx->subbeg) + i failed
2223 Previously missing files from Unicode 5.1 Character Database are now included.
2227 C<TMPDIR> is now honored when opening an anonymous temporary file
2231 =head1 Platform Specific Changes
2233 =head2 New Platforms
2239 Patches from the Haiku maintainers have been merged in. Perl should now
2244 Perl should now build on MirOS BSD.
2249 =head2 Discontinued Platforms
2255 Support for Apollo DomainOS was removed in Perl 5.11.0
2259 Support for Tenon Intersystems MachTen Unix layer for MacOS Classic was
2260 removed in Perl 5.11.0
2264 Support for Atari MiNT was removed in Perl 5.11.0.
2268 =head2 Updated Platforms
2272 =item Darwin (Mac OS X)
2278 Skip testing the be_BY.CP1131 locale on Darwin 10 (Mac OS X 10.6),
2279 as it's still buggy.
2283 Correct infelicities in the regexp used to identify buggy locales
2284 on Darwin 8 and 9 (Mac OS X 10.4 and 10.5, respectively).
2294 Fix thread library selection [perl #69686]
2304 Initial support for mingw64 is now available
2308 Various bits of Perl's build infrastructure are no longer converted to
2309 win32 line endings at release time. If this hurts you, please report the
2310 problem with the L<perlbug> program included with perl.
2314 Always add a manifest resource to C<perl.exe> to specify the C<trustInfo>
2315 settings for Windows Vista and later. Without this setting Windows
2316 will treat C<perl.exe> as a legacy application and apply various
2317 heuristics like redirecting access to protected file system areas
2318 (like the "Program Files" folder) to the users "VirtualStore"
2319 instead of generating a proper "permission denied" error.
2321 For VC8 and VC9 this manifest setting is automatically generated by
2322 the compiler/linker (together with the binding information for their
2323 respective runtime libraries); for all other compilers we need to
2324 embed the manifest resource explicitly in the external resource file.
2326 This change also requests the Microsoft Common-Controls version 6.0
2327 (themed controls introduced in Windows XP) via the dependency list
2328 in the assembly manifest. For VC8 and VC9 this is specified using the
2329 C</manifestdependency> linker commandline option instead.
2333 Improved message window handling means that C<alarm> and C<kill> messages
2334 will no longer be dropped under race conditions.
2344 Enable IPv6 support on cygwin 1.7 and newer
2354 Make -UDEBUGGING the default on VMS for 5.12.0.
2356 Like it has been everywhere else for ages and ages. Also make
2357 command-line selection of -UDEBUGGING and -DDEBUGGING work in
2358 configure.com; before the only way to turn it off was by saying
2359 no in answer to the interactive question.
2363 The default pipe buffer size on VMS has been updated to 8192 on 64-bit
2368 Reads from the in-memory temporary files of C<PerlIO::scalar> used to fail
2369 if C<$/> was set to a numeric reference (to indicate record-style reads).
2374 VMS now supports C<getgrgid>.
2378 Many improvements and cleanups have been made to the VMS file name handling
2379 and conversion code.
2383 Enabling the C<PERL_VMS_POSIX_EXIT> logical name now encodes a POSIX exit
2384 status in a VMS condition value for better interaction with GNV's bash
2385 shell and other utilities that depend on POSIX exit values. See
2386 L<perlvms/"$?"> for details.
2390 C<File::Copy> now detects Unix compatibility mode on VMS.
2396 Removed F<libbsd> for AIX 5L and 6.1. Only C<flock()> was used from F<libbsd>.
2398 Removed F<libgdbm> for AIX 5L and 6.1. The F<libgdbm> is delivered as an
2399 optional package with the AIX Toolbox. Unfortunately the 64 bit version
2402 Hints changes mean that AIX 4.2 should work again.
2406 On Cygwin we now strip the last number from the DLL. This has been the
2407 behaviour in the cygwin.com build for years. The hints files have been
2413 The hints files now identify the correct threading libraries on FreeBSD 7
2418 We now work around a bizarre preprocessor bug in the Irix 6.5 compiler:
2419 C<cc -E -> unfortunately goes into K&R mode, but C<cc -E file.c> doesn't.
2423 Hints now supports versions 5.*.
2427 Various changes from Stratus have been merged in.
2431 There is now support for Symbian S60 3.2 SDK and S60 5.0 SDK.
2435 =head1 Known Problems
2437 This is a list of some significant unfixed bugs, which are regressions
2438 from either 5.10.0 or 5.8.x.
2444 C<List::Util::first> misbehaves in the presence of a lexical C<$_>
2445 (typically introduced by C<my $_> or implicitly by C<given>). The variable
2446 which gets set for each iteration is the package variable C<$_>, not the
2447 lexical C<$_> [RT #67694].
2449 A similar issue may occur in other modules that provide functions which
2450 take a block as their first argument, like
2452 foo { ... $_ ...} list
2456 The C<charnames> pragma may generate a run-time error when a regex is
2457 interpolated [RT #56444]:
2459 use charnames ':full';
2460 my $r1 = qr/\N{THAI CHARACTER SARA I}/;
2461 "foo" =~ $r1; # okay
2462 "foo" =~ /$r1+/; # runtime error
2464 A workaround is to generate the character outside of the regex:
2466 my $a = "\N{THAI CHARACTER SARA I}";
2469 However, C<$r1> must be used within the scope of the C<use charnames> for this
2474 Some regexes may run much more slowly when run in a child thread compared
2475 with the thread the pattern was compiled into [RT #55600].
2479 Untriaged test crashes on Windows 2000
2481 Several porters have reported mysterious crashes when Perl's entire test suite is run after a build on certain Windows 2000 systems. When run by hand, the individual tests reportedly work fine.
2485 Known test failures on VMS
2487 Perl 5.11.1 fails a small set of core and CPAN tests as of this release.
2488 With luck, that'll be sorted out for 5.11.2
2492 Known test failures on VMS
2494 Perl 5.11.2 fails a small set of core and CPAN tests as of this
2495 release. With luck, that'll be sorted out for 5.11.3.
2499 =head1 Acknowledgements
2501 Perl 5.12.0 represents approximately two years of development since
2502 Perl 5.10.0 and contains __ lines of changes across ___ files
2503 from __ authors and committers:
2507 Many of the changes included in this version originated in the CPAN
2508 modules included in Perl's core. We're grateful to the entire CPAN
2509 community for helping Perl to flourish.
2511 =head1 Reporting Bugs
2513 If you find what you think is a bug, you might check the articles
2514 recently posted to the comp.lang.perl.misc newsgroup and the perl
2515 bug database at L<http://rt.perl.org/perlbug/>. There may also be
2516 information at L<http://www.perl.org/>, the Perl Home Page.
2518 If you believe you have an unreported bug, please run the B<perlbug>
2519 program included with your release. Be sure to trim your bug down
2520 to a tiny but sufficient test case. Your bug report, along with the
2521 output of C<perl -V>, will be sent off to perlbug@perl.org to be
2522 analyzed by the Perl porting team.
2524 If the bug you are reporting has security implications, which make it
2525 inappropriate to send to a publicly archived mailing list, then please send
2526 it to perl5-security-report@perl.org. This points to a closed subscription
2527 unarchived mailing list, which includes all the core committers, who be able
2528 to help assess the impact of issues, figure out a resolution, and help
2529 co-ordinate the release of patches to mitigate or fix the problem across all
2530 platforms on which Perl is supported. Please only use this address for
2531 security issues in the Perl core, not for modules independently
2532 distributed on CPAN.
2536 The F<Changes> file for an explanation of how to view exhaustive details
2539 The F<INSTALL> file for how to build Perl.
2541 The F<README> file for general stuff.
2543 The F<Artistic> and F<Copying> files for copyright information.