4 This has been logged up to 97a3247,
6 b2ea9a00b30eb5881b863d7239dd6a3721e73136
7 e4487e9b537f1be1e95aba1c87790c2a411788a7
8 68b590d93559da1f7a0d3956202180d507013365
12 [ this is a template for a new perldelta file. Any text flagged as
13 XXX needs to be processed before release. ]
15 perldelta - what is new for perl v5.13.6
19 This document describes differences between the 5.13.5 release and
22 If you are upgrading from an earlier release such as 5.13.4, first read
23 L<perl5135delta>, which describes differences between 5.13.4 and
28 XXX Any important notices here
30 =head1 Core Enhancements
32 XXX New core language features go here. Summarise user-visible core language
33 enhancements. Particularly prominent performance optimisations could go
34 here, but most should go in the L</Performance Enhancements> section.
36 [ List each enhancement as a =head2 entry ]
38 =head2 C<(?^...)> regex construct added to signify default modifiers
40 A caret (also called a "cirumflex accent") C<"^"> immediately following
41 a C<"(?"> in a regular expression now means that the subexpression is to
42 not inherit the surrounding modifiers such as C</i>, but to revert to the
43 Perl defaults. Any modifiers following the caret override the defaults.
45 The stringification of regular expressions now uses this
46 notation. E.g., before, C<qr/hlagh/i> would be stringified as
47 C<(?i-xsm:hlagh)>, but now it's stringified as C<(?^i:hlagh)>.
49 The main purpose of this is to allow tests that rely on the
50 stringification to not have to change when new modifiers are added.
51 See L<perlre/Extended Patterns>.
53 =head2 C<"d">, C<"l">, and C<"u"> regex modifiers added
55 These modifiers are currently only available within a C<(?...)> construct.
57 The C<"l"> modifier says to compile the regular expression as if it were
58 in the scope of C<use locale>, even if it is not.
60 The C<"u"> modifier says to compile the regular expression as if it were
61 in the scope of a C<use feature "unicode_strings"> pragma.
63 The C<"d"> modifier is used to override any C<use locale> and
64 C<use feature "unicode_strings"> pragmas that are in effect at the time
65 of compiling the regular expression.
67 See just below and L<perlre/(?dlupimsx-imsx)>.
69 =head2 C<use feature "unicode_strings"> now applies to some regex matching
71 Another chunk of the L<perlunicode/The "Unicode Bug"> is fixed in this
72 release. Now, regular expressions compiled within the scope of the
73 "unicode_strings" feature will match the same whether or not the target
74 string is encoded in utf8, with regard to C<\s>, C<\w>, C<\b>, and their
75 complements. Work is underway to add the C<[[:posix:]]> character
76 classes and case sensitive matching to the control of this feature, but
77 was not complete in time for this dot release.
79 =head2 C<\N{...}> now handles Unicode named character sequences
81 Unicode has a number of named character sequences, in which particular sequences
82 of code points are given names. C<\N{...}> now recognizes these.
85 =head2 New function C<charnames::string_vianame()>
87 This function is a run-time version of C<\N{...}>, returning the string
88 of characters whose Unicode name is its parameter. It can handle
89 Unicode named character sequences, whereas the pre-existing
90 C<charnames::vianame()> cannot, as the latter returns a single code
94 =head2 Reentrant regular expression engine
96 It is now safe to use regular expressions within C<(?{...})> and
97 C<(??{...})> code blocks inside regular expressions.
99 These block are still experimental, however, and still have problems with
100 lexical (C<my>) variables, lexical pragmata and abnormal exiting.
102 =head2 Custom per-subroutine check hooks
104 XS code in an extension module can now annotate a subroutine (whether
105 implemented in XS or in Perl) so that nominated XS code will be called
106 at compile time (specifically as part of op checking) to change the op
107 tree of that subroutine. The compile-time check function (supplied by
108 the extension module) can implement argument processing that can't be
109 expressed as a prototype, generate customised compile-time warnings,
110 perform constant folding for a pure function, inline a subroutine
111 consisting of sufficiently simple ops, replace the whole call with a
112 custom op, and so on. This was previously all possible by hooking the
113 C<entersub> op checker, but the new mechanism makes it easy to tie the
114 hook to a specific subroutine. See L<perlapi/cv_set_call_checker>.
116 To help in writing custom check hooks, several subtasks within standard
117 C<entersub> op checking have been separated out and exposed in the API.
119 =head2 Return value of C<delete $+{...}>
121 Custom regular expression engines can now determine the return value of
122 C<delete> on an entry of C<%+> or C<%->.
126 XXX Any security-related notices go here. In particular, any security
127 vulnerabilities closed should be noted here rather than in the
128 L</Selected Bug Fixes> section.
130 [ List each security issue as a =head2 entry ]
132 =head1 Incompatible Changes
134 =head2 Stringification of regexes has changed
136 Default regular expression modifiers are now notated by using
137 C<(?^...)>. Code relying on the old stringification will fail. The
138 purpose of this is so that when new modifiers are added, such code will
139 not have to change (after this one time), as the stringification will
140 automatically incorporate the new modifiers.
142 Code that needs to work properly with both old- and new-style regexes
143 can avoid the whole issue by using (for Perls since 5.9.5):
145 use re qw(regexp_pattern);
146 my ($pat, $mods) = regexp_pattern($re_ref);
148 where C<$re_ref> is a reference to a compiled regular expression. Upon
149 return, C<$mods> will be a string containing all the non-default
150 modifiers used when the regular expression was compiled, and C<$pattern>
153 If the actual stringification is important, or older Perls need to be
154 supported, you can use something like the following:
156 # Accept both old and new-style stringification
157 my $modifiers = (qr/foobar/ =~ /\Q(?^/) ? '^' : '-xism';
159 And then use C<$modifiers> instead of C<-xism>.
161 =head2 Regular expressions retain their localeness when interpolated
163 Regular expressions compiled under C<"use locale"> now retain this when
164 interpolated into a new regular expression compiled outside a
165 C<"use locale">, and vice-versa.
167 Previously, a regular expression interpolated into another one inherited
168 the localeness of the surrounding one, losing whatever state it
169 originally had. This is considered a bug fix, but may trip up code that
170 has come to rely on the incorrect behavior.
172 =head2 Directory handles not copied to threads
174 On systems that do not have a C<fchdir> function, newly-created threads no
175 longer inherit directory handles from their parent threads. Such programs
176 would probably have crashed anyway
177 L<[perl #75154]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=75154>.
179 =head2 Negation treats strings differently from before
181 The unary negation operator C<-> now treats strings that look like numbers
183 L<[perl #57706]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=57706>.
187 Negative zero (-0.0), when converted to a string, now becomes "0" on all
188 platforms. It used to become "-0" on some, but "0" on others.
190 If you still need to determine whether a zero is negative, use
191 C<sprintf("%g", $zero) =~ /^-/> or the L<Data::Float> module on CPAN.
195 XXX Any deprecated features, syntax, modules etc. should be listed here.
196 In particular, deprecated modules should be listed here even if they are
197 listed as an updated module in the L</Modules and Pragmata> section.
199 [ List each deprecation as a =head2 entry ]
201 =head1 Performance Enhancements
203 XXX Changes which enhance performance without changing behaviour go here. There
204 may well be none in a stable release.
206 [ List each enhancement as a =item entry ]
212 The bulk of the C<Tie::Hash::NamedCapture> module used to be in the perl
213 core. It has now been moved to an XS module, to reduce the overhead for
214 programs that do not use C<%+> or C<%->.
218 =head1 Modules and Pragmata
220 XXX All changes to installed files in F<cpan/>, F<dist/>, F<ext/> and F<lib/>
221 go here. If Module::CoreList is updated, generate an initial draft of the
222 following sections using F<Porting/corelist-perldelta.pl>, which prints stub
223 entries to STDOUT. Results can be pasted in place of the '=head2' entries
224 below. A paragraph summary for important changes should then be added by hand.
225 In an ideal world, dual-life modules would have a F<Changes> file that could be
228 [ Within each section, list entries as a =item entry ]
230 =head2 New Modules and Pragmata
240 =head2 Updated Modules and Pragmata
246 C<Archive::Extract> has been upgraded from version 0.42 to 0.44
250 C<Carp> has been upgraded from version 1.18 to 1.19.
252 It no longer autovivifies the C<*CORE::GLOBAL::caller> glob, something it
253 started doing in 1.18, which was released with perl 5.13.4
254 L<[perl #78082]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=78082>
258 C<Data::Dumper> has been upgraded from version 2.128 to 2.129.
260 C<Dumpxs> no longer crashes with globs returned by C<*$io_ref>
261 L<[perl #72332]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=72332>.
265 C<Digest::MD5> has been upgraded from version 2.40 to 2.51.
267 It is now safe to use this module in combination with threads.
271 C<File::DosGlob> has been upgraded from version 1.02 to 1.03.
273 It allows patterns containing literal parentheses (they no longer need to
274 be escaped). On Windows, it no longer adds an extra F<./> to the file names
275 returned when the pattern is a relative glob with a drive specification,
277 L<[perl #71712]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=71712>.
281 C<File::Find> has been upgraded from version 1.17 to 1.18.
283 It improves handling of backslashes on Windows, so that paths such as
284 F<c:\dir\/file> are no longer generated
285 L<[perl #71710]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=71710>.
289 C<if> has been upgraded from version 0.05 to 0.06
293 C<IPC::Open3> has been upgraded from version 1.06 to 1.07.
295 The internal C<xclose> routine now knows how to handle file descriptors, as
296 documented, so duplicating STDIN in a child process using its file
298 L<[perl #76474]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=71710>.
302 C<Locale::Codes> has been upgraded from version 3.13 to 3.14.
306 C<Locale::Maketext> has been upgraded from version 1.15 to 1.16.
308 It fixes an infinite loop in C<Locale::Maketext::Guts::_compile()> when
309 working with tainted values
310 (L<CPAN RT #40727|https://rt.cpan.org/Public/Bug/Display.html?id=40727>).
312 C<< ->maketext >> calls will now backup and restore C<$@> so that error
313 messages are not supressed
314 (L<CPAN RT #34182|https://rt.cpan.org/Public/Bug/Display.html?id=34182>).
318 C<Math::BigInt> has been upgraded from version 1.95 to 1.97.
320 This prevents C<sqrt($int)> from crashing under C<use bigrat;>
321 L<[perl #73534]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=73534>.
325 C<NEXT> has been upgraded from version 0.64 to 0.65.
329 C<overload> has been upgraded from version 1.10 to 1.11.
331 C<overload::Method> can now handle subroutines that are themselves blessed
332 into overloaded classes
333 L<[perl #71998]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=71998>.
337 C<PathTools> has been upgraded from version 3.31_01 to 3.34.
341 C<sigtrap> has been upgraded from version 1.04 to 1.05.
343 It no longer tries to modify read-only arguments when generating a
345 L<[perl #72340]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=72340>.
349 C<threads> has been upgraded from version 1.77_03 to 1.81_01.
353 C<threads::shared> has been upgrade from version 1.33_03 to 1.34
357 C<Unicode::Collate> has been upgraded from version 0.59 to 0.63
359 U::C::Locale newly supports locales: ar, be, bg, de__phonebook, hu, hy, kk, mk, nso, om,
360 tn, vi, hr, ig, ru, sq, se, sr, to and uk
364 C<Unicode::Normalize> has been upgraded from version 1.06 to 1.07
368 =head2 Removed Modules and Pragmata
380 XXX Changes to files in F<pod/> go here. Consider grouping entries by
381 file and be sure to link to the appropriate page, e.g. L<perlfunc>.
383 =head2 New Documentation
385 XXX Changes which create B<new> files in F<pod/> go here.
389 XXX Description of the purpose of the new file here
391 =head2 Changes to Existing Documentation
393 XXX Changes which significantly change existing files in F<pod/> go here.
394 However, any changes to F<pod/perldiag.pod> should go in the L</Diagnostics>
403 The documentation for the C<SvTRUE> macro was simply wrong in stating that
404 get-magic is not processed. It has been corrected.
410 The following additions or changes have been made to diagnostic output,
411 including warnings and fatal error messages. For the complete list of
412 diagnostic messages, see L<perldiag>.
414 XXX New or changed warnings emitted by the core's C<C> code go here. Also
415 include any changes in L<perldiag> that reconcile it to the C<C> code.
417 [ Within each section, list entries as a =item entry ]
419 =head2 New Diagnostics
421 XXX Newly added diagnostic messages go here
431 =head2 Changes to Existing Diagnostics
433 XXX Changes (i.e. rewording) of diagnostic messages go here
439 The 'Layer does not match this perl' error message has been replaced with
440 these more helpful messages:
446 PerlIO layer function table size (%d) does not match size expected by this
451 PerlIO layer instance size (%d) does not match size expected by this perl
456 L<[perl #73754]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=73754>
460 =head1 Utility Changes
462 XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go
463 here. Most of these are built within the directories F<utils> and F<x2p>.
465 [ List utility changes as a =head3 entry for each utility and =item
466 entries for each change
467 Use L<XXX> with program names to get proper documentation linking. ]
479 =head1 Configuration and Compilation
481 XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
482 go here. Any other changes to the Perl build process should be listed here.
483 However, any platform-specific changes should be listed in the
484 L</Platform Support> section, instead.
486 [ List changes as a =item entry ].
498 XXX Any significant changes to the testing of a freshly built perl should be
499 listed here. Changes which create B<new> files in F<t/> go here as do any
500 large changes to the testing harness (e.g. when parallel testing was added).
501 Changes to existing files in F<t/> aren't worth summarising, although the bugs
502 that they represent may be covered elsewhere.
504 [ List each test improvement as a =item entry ]
510 The script F<t/op/threads-dirh.t> has been added, which tests interaction
511 of threads and directory handles.
515 =head1 Platform Support
517 XXX Any changes to platform support should be listed in the sections below.
519 [ Within the sections, list each platform as a =item entry with specific
520 changes as paragraphs below it. ]
524 XXX List any platforms that this version of perl compiles on, that previous
525 versions did not. These will either be enabled by new files in the F<hints/>
526 directories, or new subdirectories and F<README> files at the top level of the
531 =item XXX-some-platform
537 =head2 Discontinued Platforms
539 XXX List any platforms that this version of perl no longer compiles on.
543 =item XXX-some-platform
549 =head2 Platform-Specific Notes
551 XXX List any changes for specific platforms. This could include configuration
552 and compilation changes or changes in portability/compatibility. However,
553 changes within modules for platforms should generally be listed in the
554 L</Modules and Pragmata> section.
560 Conversion of strings to floating-point numbers is now more accurate on
562 L<[perl #32380]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=32380>.
566 Early versions of Mac OS X (Darwin) had buggy implementations of the
567 C<setregid>, C<setreuid>, C<setrgid> and C<setruid> functions, so perl
568 would pretend they did not exist.
570 These functions are now recognised on Mac OS 10.5 (Leopard; Darwin 9) and
571 higher, as they have been fixed
572 L<[perl #72990]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=72990>.
576 perl now builds again with OpenVOS (formerly known as Stratus VOS)
577 L<[perl #78132]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=78132>.
581 The shortening of symbols longer than 31 characters in the C sources is
582 now done by the compiler rather than by xsubpp (which could only do so
583 for generated symbols in XS code).
587 C<$Config{gccversion}> is now set correctly when perl is built using the
588 mingw64 compiler from L<http://mingw64.org>
589 L<[perl #73754]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=73754>.
591 The build process proceeds more smoothly with mingw and dmake when
592 F<C:\MSYS\bin> is in the PATH, due to a C<Cwd> fix.
596 =head1 Internal Changes
598 XXX Changes which affect the interface available to C<XS> code go here.
599 Other significant internal changes for future core maintainers should
602 [ List each test improvement as a =item entry ]
608 See L</Regular expressions retain their localeness when interpolated>,
613 The C<sv_cmp_flags>, C<sv_cmp_locale_flags>, C<sv_eq_flags> and
614 C<sv_collxfrm_flags> functions have been added. These are like their
615 non-_flags counterparts, but allow one to specify whether get-magic is
618 The C<sv_cmp>, C<sv_cmp_locale>, C<sv_eq> and C<sv_collxfrm> functions have
619 been replaced with wrappers around the new functions.
623 A new C<sv_2bool_flags> function has been added.
625 This is like C<sv_2bool>, but it lets the calling code decide whether
626 get-magic is handled. C<sv_2bool> is now a macro that calls the new
631 A new macro, C<SvTRUE_nomg>, has been added.
633 This is like C<SvTRUE>, except that it does not process magic. It uses the
634 new C<sv_2bool_flags> function.
638 C<sv_catsv_flags> no longer calls C<mg_get> on its second argument (the
639 source string) if the flags passed to it do not include SV_GMAGIC. So it
640 now matches the documentation.
644 A new interface has been added for custom check hooks on subroutines. See
645 L/Custom per-subroutine check hooks>, above.
649 List op building functions have been added to the
650 API. See L<op_append_elem|perlapi/op_append_elem>,
651 L<op_append_list|perlapi/op_append_list>, and
652 L<op_prepend_elem|perlapi/op_prepend_elem>.
656 The L<LINKLIST|perlapi/LINKLIST> macro, part of op building that
657 constructs the execution-order op chain, has been added to the API.
661 Many functions ending with pvn now have equivalent pv/pvs/sv versions.
665 The C<save_freeop>, C<save_op>, C<save_pushi32ptr> and C<save_pushptrptr>
666 functions have been added to the API.
670 The new API function C<parse_stmtseq()> parses a sequence of statements, up
671 to closing brace or EOF.
675 =head1 Selected Bug Fixes
677 XXX Important bug fixes in the core language are summarised here.
678 Bug fixes in files in F<ext/> and F<lib/> are best summarised in
679 L</Modules and Pragmata>.
681 [ List each fix as a =item entry ]
687 A regular expression match in the right-hand side of a global substitution
688 (C<s///g>) that is in the same scope will no longer cause match variables
689 to have the wrong values on subsequent iterations. This can happen when an
690 array or hash subscript is interpolated in the right-hand side, as in
691 C<s|(.)|@a{ print($1), /./ }|g>
692 L<[perl #19078]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=19078>.
696 Constant-folding used to cause
698 $text =~ ( 1 ? /phoo/ : /bear/)
704 at compile time. Now it correctly matches against C<$_>
705 L<[perl #20444]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=20444>.
709 Parsing Perl code (either with string C<eval> or by loading modules) from
710 within a C<UNITCHECK> block no longer causes the interpreter to crash
711 L<[perl #70614]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=70614>.
715 When C<-d> is used on the shebang (C<#!>) line, the debugger now has access
716 to the lines of the main program. In the past, this sometimes worked and
717 sometimes did not, depending on what order things happened to be arranged
719 L<[perl #71806]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=71806>.
723 The C<y///> or C<tr///> operator now calls get-magic (e.g., the C<FETCH>
724 method of a tie) on its left-hand side just once, not twice
725 L<[perl #76814]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=76814>.
729 String comparison (C<eq>, C<ne>, C<lt>, C<gt>, C<le>, C<ge> and
730 C<cmp>) and logical not (C<not> and C<!>) operators no longer call magic
731 (e.g., tie methods) twice on their operands
732 L<[perl #76814]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=76814>.
734 This bug was introduced in an earlier 5.13 release, and does not affect
739 When a tied (or other magic) variable is used as, or in, a regular
740 expression, it no longer has its C<FETCH> method called twice
741 L<[perl #76814]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=76814>.
743 This bug was introduced in an earlier 5.13 release, and does not affect
748 The C<-C> command line option can now be followed by other options
749 L<[perl #72434]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=72434>.
753 Assigning a glob to a PVLV used to convert it to a plain string. Now it
754 works correctly, and a PVLV can hold a glob. This would happen when a
755 nonexistent hash or array element was passed to a subroutine:
757 sub { $_[0] = *foo }->($hash{key});
758 # $_[0] would have been the string "*main::foo"
760 It also happened when a glob was assigned to, or returned from, an element
761 of a tied array or hash
762 L<[perl #36051]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=36051>.
766 Creating a new thread when directory handles were open used to cause a
767 crash, because the handles were not cloned, but simply passed to the new
768 thread, resulting in a double free.
770 Now directory handles are cloned properly, on systems that have a C<fchdir>
771 function. On other systems, new threads simply do not inherit directory
772 handles from their parent threads
773 L<[perl #75154]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=75154>.
777 The regular expression parser no longer hangs when parsing C<\18> and
780 This bug was introduced in version 5.13.5 and did not affect earlier
782 L<[perl #78058]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=78058>.
786 Subroutine redefinition works once more in the debugger
787 L<[perl #48332]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=48332>.
791 The C<&> C<|> C<^> bitwise operators no longer coerce read-only arguments
792 L<[perl #20661]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=20661>.
796 Stringifying a scalar containing -0.0 no longer has the affect of turning
798 L<[perl #45133]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=45133>.
802 Aliasing packages by assigning to globs or deleting packages by deleting
803 their containing stash elements used to have erratic effects on method
804 resolution, because the internal 'isa' caches were not reset. This has been
809 C<sort> with a custom sort routine could crash if too many nested
810 subroutine calls occurrred from within the sort routine
811 L<[perl #77930]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=77930>.
813 This bug was introduced in an earlier 5.13 release, and did not affect
818 The C<eval_sv> and C<eval_pv> C functions now set C<$@> correctly when
819 there is a syntax error and no C<G_KEEPERR> flag, and never set it if the
820 C<G_KEEPERR> flag is present
821 L<[perl #3719]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=3719>.
825 Nested C<map> and C<grep> blocks no longer leak memory when processing
827 L<[perl #48004]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=48004>.
831 Malformed C<version> objects no longer cause crashes
832 L<[perl #78286]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=78286>.
836 The interpreter no longer crashes when freeing deeply-nested arrays of
837 arrays. Hashes have not been fixed yet
838 L<[perl #44225]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=44225>.
842 The mechanism for freeing objects in globs used to leave dangling
843 pointers to freed SVs, meaning Perl users could see corrupted state
846 Perl now only frees the affected slots of the GV, rather than freeing
847 the GV itself. This makes sure that there are no dangling refs or
848 corrupted state during destruction.
852 Perl no longer leaks C<PL_main_cv> or C<PL_defstash> during
853 destruction L<[perl #40388]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=40388>.
857 =head1 Known Problems
859 XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
860 tests that had to be C<TODO>ed for the release would be noted here, unless
861 they were specific to a particular platform (see below).
863 This is a list of some significant unfixed bugs, which are regressions
864 from either 5.XXX.XXX or 5.XXX.XXX.
866 [ List each fix as a =item entry ]
878 XXX If any significant core contributor has died, we've added a short obituary
887 Fixed a typo in L<perl5135delta> regarding array slices and smart matching
891 =head1 Acknowledgements
893 XXX The list of people to thank goes here.
895 =head1 Reporting Bugs
897 If you find what you think is a bug, you might check the articles
898 recently posted to the comp.lang.perl.misc newsgroup and the perl
899 bug database at http://rt.perl.org/perlbug/ . There may also be
900 information at http://www.perl.org/ , the Perl Home Page.
902 If you believe you have an unreported bug, please run the B<perlbug>
903 program included with your release. Be sure to trim your bug down
904 to a tiny but sufficient test case. Your bug report, along with the
905 output of C<perl -V>, will be sent off to perlbug@perl.org to be
906 analysed by the Perl porting team.
908 If the bug you are reporting has security implications, which make it
909 inappropriate to send to a publicly archived mailing list, then please send
910 it to perl5-security-report@perl.org. This points to a closed subscription
911 unarchived mailing list, which includes all the core committers, who be able
912 to help assess the impact of issues, figure out a resolution, and help
913 co-ordinate the release of patches to mitigate or fix the problem across all
914 platforms on which Perl is supported. Please only use this address for
915 security issues in the Perl core, not for modules independently
920 The F<Changes> file for an explanation of how to view exhaustive details
923 The F<INSTALL> file for how to build Perl.
925 The F<README> file for general stuff.
927 The F<Artistic> and F<Copying> files for copyright information.