5 [ this is a template for a new perldelta file. Any text flagged as XXX needs
6 to be processed before release. ]
8 perldelta - what is new for perl v5.17.7
12 This document describes differences between the 5.17.6 release and the 5.17.7
15 If you are upgrading from an earlier release such as 5.17.5, first read
16 L<perl5176delta>, which describes differences between 5.17.5 and 5.17.6.
20 XXX Any important notices here
22 =head1 Core Enhancements
24 =head2 $&, $` and $' are no longer slow
26 These three infamous variables have been redeemed and no longer slow down
27 your program when used. Hence, the /p regular expression flag now does
32 XXX Any security-related notices go here. In particular, any security
33 vulnerabilities closed should be noted here rather than in the
34 L</Selected Bug Fixes> section.
36 [ List each security issue as a =head2 entry ]
38 =head1 Incompatible Changes
40 =head2 readline() with C<$/ = \N> now reads N characters, not N bytes
42 Previously, when reading from a stream with I/O layers such as
43 C<encoding>, the readline() function, otherwise known as the C<< <> >>
44 operator, would read I<N> bytes from the top-most layer. [perl #79960]
46 Now, I<N> characters are read instead.
48 There is no change in behaviour when reading from streams with no
49 extra layers, since bytes map exactly to characters.
51 =head2 Lexical subroutine warnings have moved
53 The warning about the use of an experimental feature emitted when lexical
54 subroutines (added in 5.17.4) are used now happens when the subroutine
55 itself is declared, not when the "lexical_subs" feature is activated via
58 This stops C<use feature ':all'> from warning, but causes
59 C<my sub foo; my sub bar> to warn twice.
63 XXX Any deprecated features, syntax, modules etc. should be listed here. In
64 particular, deprecated modules should be listed here even if they are listed as
65 an updated module in the L</Modules and Pragmata> section.
67 [ List each deprecation as a =head2 entry ]
69 =head2 Lexical $_ is now deprecated
71 Since it was introduced in Perl 5.10, it has caused much confusion with no
78 Various modules (e.g., List::Util) expect callback routines to use the
79 global $_. C<use List::Util 'first'; my $_; first { $_ == 1 } @list> does
80 not work as one would expect.
84 A C<my $_> declaration earlier in the same file can cause confusing closure
89 The "_" subroutine prototype character allows called subroutines to access
90 your lexical $_, so it is not really private after all.
94 Nevertheless, subroutines with a "(@)" prototype and methods cannot access
95 the caller's lexical $_, unless they are written in XS.
99 But even XS routines cannot access a lexical $_ declared, not in the
100 calling subroutine, but in an outer scope, iff that subroutine happened not
101 to mention $_ or use any operators that default to $_.
105 =head2 Various XS-callable functions are now deprecated
107 The following functions will be removed from a future version of Perl,
108 and should not be used. With participating C compilers (e.g., gcc),
109 compiling any file that uses any of these will generate a warning.
110 These were not intended for public use; there are equivalent, faster,
111 macros for most of them. See L<perlapi/Character classes>:
118 C<is_uni_idfirst_lc>,
128 C<is_utf8_perl_space>,
129 C<is_utf8_perl_word>,
130 C<is_utf8_posix_digit>,
140 =head1 Performance Enhancements
142 XXX Changes which enhance performance without changing behaviour go here.
143 There may well be none in a stable release.
145 [ List each enhancement as a =item entry ]
151 Perl has a new copy-on-write mechanism that avoids the need to copy the
152 internal string buffer when assigning from one scalar to another. This
153 makes copying large strings appear much faster. Modifying one of the two
154 (or more) strings after an assignment will force a copy internally. This
155 makes it unnecessary to pass strings by reference for efficiency.
159 =head1 Modules and Pragmata
161 XXX All changes to installed files in F<cpan/>, F<dist/>, F<ext/> and F<lib/>
162 go here. If Module::CoreList is updated, generate an initial draft of the
163 following sections using F<Porting/corelist-perldelta.pl>, which prints stub
164 entries to STDOUT. Results can be pasted in place of the '=head2' entries
165 below. A paragraph summary for important changes should then be added by hand.
166 In an ideal world, dual-life modules would have a F<Changes> file that could be
169 [ Within each section, list entries as a =item entry ]
171 =head2 New Modules and Pragmata
181 =head2 Updated Modules and Pragmata
187 L<GDBM_File> has been upgraded from version 1.14 to 1.15. The undocumented
188 optional fifth parameter to C<TIEHASH> has been removed. This was intended
189 to provide control of the callback used by C<gdbm*> functions in case of
190 fatal errors (such as filesystem problems), but did not work (and could
191 never have worked). No code on CPAN even attempted to use it. The callback
192 is now always the previous default, C<croak>. Problems on some platforms with
193 how the C<C> C<croak> function is called have also been resolved.
197 =head2 Removed Modules and Pragmata
209 XXX Changes to files in F<pod/> go here. Consider grouping entries by
210 file and be sure to link to the appropriate page, e.g. L<perlfunc>.
212 =head2 New Documentation
214 XXX Changes which create B<new> files in F<pod/> go here.
218 XXX Description of the purpose of the new file here
220 =head2 Changes to Existing Documentation
222 XXX Changes which significantly change existing files in F<pod/> go here.
223 However, any changes to F<pod/perldiag.pod> should go in the L</Diagnostics>
226 =head3 L<perlapi/Character classes>
232 There are quite a few macros callable from XS modules that classify
233 characters into things like alphabetic, punctuation, etc. More of these
234 are now documented, including ones which work on characters whose code
235 points are outside the Latin-1 range.
241 The following additions or changes have been made to diagnostic output,
242 including warnings and fatal error messages. For the complete list of
243 diagnostic messages, see L<perldiag>.
245 XXX New or changed warnings emitted by the core's C<C> code go here. Also
246 include any changes in L<perldiag> that reconcile it to the C<C> code.
248 =head2 New Diagnostics
250 XXX Newly added diagnostic messages go under here, separated into New Errors
259 XXX L<message|perldiag/"message">
269 XXX L<message|perldiag/"message">
273 =head2 Changes to Existing Diagnostics
275 XXX Changes (i.e. rewording) of diagnostic messages go here
281 XXX Describe change here
285 =head1 Utility Changes
287 XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go here.
288 Most of these are built within the directories F<utils> and F<x2p>.
290 [ List utility changes as a =head3 entry for each utility and =item
291 entries for each change
292 Use L<XXX> with program names to get proper documentation linking. ]
304 =head1 Configuration and Compilation
306 XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
307 go here. Any other changes to the Perl build process should be listed here.
308 However, any platform-specific changes should be listed in the
309 L</Platform Support> section, instead.
311 [ List changes as a =item entry ].
323 XXX Any significant changes to the testing of a freshly built perl should be
324 listed here. Changes which create B<new> files in F<t/> go here as do any
325 large changes to the testing harness (e.g. when parallel testing was added).
326 Changes to existing files in F<t/> aren't worth summarizing, although the bugs
327 that they represent may be covered elsewhere.
329 [ List each test improvement as a =item entry ]
339 =head1 Platform Support
341 XXX Any changes to platform support should be listed in the sections below.
343 [ Within the sections, list each platform as a =item entry with specific
344 changes as paragraphs below it. ]
348 XXX List any platforms that this version of perl compiles on, that previous
349 versions did not. These will either be enabled by new files in the F<hints/>
350 directories, or new subdirectories and F<README> files at the top level of the
355 =item XXX-some-platform
361 =head2 Discontinued Platforms
367 Support for BeOS has been removed.
371 =head2 Platform-Specific Notes
373 XXX List any changes for specific platforms. This could include configuration
374 and compilation changes or changes in portability/compatibility. However,
375 changes within modules for platforms should generally be listed in the
376 L</Modules and Pragmata> section.
380 =item XXX-some-platform
386 =head1 Internal Changes
388 XXX Changes which affect the interface available to C<XS> code go here. Other
389 significant internal changes for future core maintainers should be noted as
392 [ List each change as a =item entry ]
398 SvUPGRADE() is no longer an expression. Originally this macro (and its
399 underlying function, sv_upgrade()) were documented as boolean, although
400 in reality they always croaked on error and never returned false. In 2005
401 the documentation was updated to specify a void return value, but
402 SvUPGRADE() was left always returning 1 for backwards compatibility. This
403 has now been removed, and SvUPGRADE() is now a statement with no return
406 So this is now a syntax error:
408 if (!SvUPGRADE(sv)) { croak(...); }
410 If you have code like that, simply replace it with
414 or to to avoid compiler warnings with older perls, possibly
420 Perl has a new copy-on-write mechanism that allows any SvPOK scalar to be
421 upgraded to a copy-on-write scalar. A reference count on the string buffer
422 is stored in the string buffer itself.
424 This breaks a few XS modules by allowing copy-on-write scalars to go
425 through code paths that never encountered them before.
427 This behaviour can still be disabled by running F<Configure> with
428 B<-Accflags=-DPERL_NO_COW>. This option will probably be removed in Perl
433 Copy-on-write no longer uses the SvFAKE and SvREADONLY flags. Hence,
434 SvREADONLY indicates a true read-only SV.
436 Use the SvIsCOW macro (as before) to identify a copy-on-write scalar.
440 C<PL_sawampersand> is now a constant. The switch this variable provided
441 (to enable/disable the pre-match copy depending on whether C<$&> had been
442 seen) has been removed and replaced with copy-on-write, eliminating a few
445 The previous behaviour can still be enabled by running F<Configure> with
446 B<-Accflags=-DPERL_SAWAMPERSAND>.
450 =head1 Selected Bug Fixes
452 XXX Important bug fixes in the core language are summarized here. Bug fixes in
453 files in F<ext/> and F<lib/> are best summarized in L</Modules and Pragmata>.
455 [ List each fix as a =item entry ]
461 C<sort {undef} ...> under fatal warnings no longer crashes. It started
462 crashing in Perl 5.16.
466 Stashes blessed into each other
467 (C<bless \%Foo::, 'Bar'; bless \%Bar::, 'Foo'>) no longer result in double
468 frees. This bug started happening in Perl 5.16.
472 Numerous memory leaks have been fixed, mostly involving fatal warnings and
477 Lexical constants (C<my sub answer () { 42 }>) no longer cause double
482 Constant subroutine redefinition warns by default, but lexical constants
483 were accidentally exempt from default warnings. This has been corrected.
487 Some failed regular expression matches such as C<'f' =~ /../g> were not
488 resetting C<pos>. Also, "match-once" patterns (C<m?...?g>) failed to reset
489 it, too, when invoked a second time [perl #23180].
493 Accessing C<$&> after a pattern match now works if it had not been seen
494 before the match. I.e., this applies to C<${'&'}> (under C<no strict>) and
495 C<eval '$&'>. The same applies to C<$'> and C<$`> [perl #4289].
499 Several bugs involving C<local *ISA> and C<local *Foo::> causing stale
500 MRO caches have been fixed.
504 Defining a subroutine when its typeglob has been aliased no longer results
505 in stale method caches. This bug was introduced in Perl 5.10.
509 Localising a typeglob containing a subroutine when the typeglob's package
510 has been deleted from its parent stash no longer produces an error. This
511 bug was introduced in Perl 5.14.
515 Under some circumstances, C<local *method=...> would fail to reset method
516 caches upon scope exit.
520 C</[.foo.]/> is no longer an error, but produces a warning (as before) and
521 is treated as C</[.fo]/> [perl #115818].
525 C<goto $tied_var> now calls FETCH before deciding what type of goto
526 (subroutine or label) this is.
530 =head1 Known Problems
532 XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
533 tests that had to be C<TODO>ed for the release would be noted here. Unfixed
534 platform specific bugs also go here.
536 [ List each fix as a =item entry ]
548 XXX If any significant core contributor has died, we've added a short obituary
551 =head1 Acknowledgements
553 XXX Generate this with:
555 perl Porting/acknowledgements.pl v5.17.6..HEAD
557 =head1 Reporting Bugs
559 If you find what you think is a bug, you might check the articles recently
560 posted to the comp.lang.perl.misc newsgroup and the perl bug database at
561 http://rt.perl.org/perlbug/ . There may also be information at
562 http://www.perl.org/ , the Perl Home Page.
564 If you believe you have an unreported bug, please run the L<perlbug> program
565 included with your release. Be sure to trim your bug down to a tiny but
566 sufficient test case. Your bug report, along with the output of C<perl -V>,
567 will be sent off to perlbug@perl.org to be analysed by the Perl porting team.
569 If the bug you are reporting has security implications, which make it
570 inappropriate to send to a publicly archived mailing list, then please send it
571 to perl5-security-report@perl.org. This points to a closed subscription
572 unarchived mailing list, which includes all the core committers, who will be
573 able to help assess the impact of issues, figure out a resolution, and help
574 co-ordinate the release of patches to mitigate or fix the problem across all
575 platforms on which Perl is supported. Please only use this address for
576 security issues in the Perl core, not for modules independently distributed on
581 The F<Changes> file for an explanation of how to view exhaustive details on
584 The F<INSTALL> file for how to build Perl.
586 The F<README> file for general stuff.
588 The F<Artistic> and F<Copying> files for copyright information.