path: root/pod/perl5136delta.pod

=encoding utf8

=head1 NAME

perl5136delta - what is new for perl v5.13.6

=head1 DESCRIPTION

This document describes differences between the 5.13.5 release and
the 5.13.6 release.

If you are upgrading from an earlier release such as 5.13.4, first read
L<perl5135delta>, which describes differences between 5.13.4 and
5.13.5.

=head1 Core Enhancements

=head2  C<(?^...)> regex construct added to signify default modifiers

A caret (also called a "cirumflex accent") C<"^"> immediately following
a C<"(?"> in a regular expression now means that the subexpression is to
not inherit the surrounding modifiers such as C</i>, but to revert to the
Perl defaults.  Any modifiers following the caret override the defaults.

The stringification of regular expressions now uses this
notation.  E.g., before, C<qr/hlagh/i> would be stringified as
C<(?i-xsm:hlagh)>, but now it's stringified as C<(?^i:hlagh)>.

The main purpose of this is to allow tests that rely on the
stringification to not have to change when new modifiers are added.
See L<perlre/Extended Patterns>.

=head2 C<"d">, C<"l">, and C<"u"> regex modifiers added

These modifiers are currently only available within a C<(?...)> construct.

The C<"l"> modifier says to compile the regular expression as if it were
in the scope of C<use locale>, even if it is not.

The C<"u"> modifier says to compile the regular expression as if it were
in the scope of a C<use feature "unicode_strings"> pragma.

The C<"d"> modifier is used to override any C<use locale> and
C<use feature "unicode_strings"> pragmas that are in effect at the time
of compiling the regular expression.

See just below and L<perlre/(?dlupimsx-imsx)>.

=head2 C<use feature "unicode_strings"> now applies to some regex matching

Another chunk of the L<perlunicode/The "Unicode Bug"> is fixed in this
release.  Now, regular expressions compiled within the scope of the
"unicode_strings" feature will match the same whether or not the target
string is encoded in utf8, with regard to C<\s>, C<\w>, C<\b>, and their
complements.  Work is underway to add the C<[[:posix:]]> character
classes and case sensitive matching to the control of this feature, but
was not complete in time for this dot release.

=head2 C<\N{...}> now handles Unicode named character sequences

Unicode has a number of named character sequences, in which particular sequences
of code points are given names.  C<\N{...}> now recognizes these.
See L<charnames>.

=head2 New function C<charnames::string_vianame()>

This function is a run-time version of C<\N{...}>, returning the string
of characters whose Unicode name is its parameter.  It can handle
Unicode named character sequences, whereas the pre-existing
C<charnames::vianame()> cannot, as the latter returns a single code
point.
See L<charnames>.

=head2 Reentrant regular expression engine

It is now safe to use regular expressions within C<(?{...})> and
C<(??{...})> code blocks inside regular expressions.

These block are still experimental, however, and still have problems with
lexical (C<my>) variables, lexical pragmata and abnormal exiting.

=head2 Custom per-subroutine check hooks

XS code in an extension module can now annotate a subroutine (whether
implemented in XS or in Perl) so that nominated XS code will be called
at compile time (specifically as part of op checking) to change the op
tree of that subroutine.  The compile-time check function (supplied by
the extension module) can implement argument processing that can't be
expressed as a prototype, generate customised compile-time warnings,
perform constant folding for a pure function, inline a subroutine
consisting of sufficiently simple ops, replace the whole call with a
custom op, and so on.  This was previously all possible by hooking the
C<entersub> op checker, but the new mechanism makes it easy to tie the
hook to a specific subroutine.  See L<perlapi/cv_set_call_checker>.

To help in writing custom check hooks, several subtasks within standard
C<entersub> op checking have been separated out and exposed in the API.

=head2 Return value of C<delete $+{...}>

Custom regular expression engines can now determine the return value of
C<delete> on an entry of C<%+> or C<%->.

=head2 C<keys>, C<values> work on arrays

You can now use the C<keys>, C<values>, C<each> builtin functions on arrays
(previously you could only use them on hashes).  See L<perlfunc> for details.
This is actually a change introduced in perl 5.12.0, but it was missed from
that release's perldelta.

=head1 Incompatible Changes

=head2 Stringification of regexes has changed

Default regular expression modifiers are now notated by using
C<(?^...)>.  Code relying on the old stringification will fail.  The
purpose of this is so that when new modifiers are added, such code will
not have to change (after this one time), as the stringification will
automatically incorporate the new modifiers.

Code that needs to work properly with both old- and new-style regexes
can avoid the whole issue by using (for Perls since 5.9.5):

 use re qw(regexp_pattern);
 my ($pat, $mods) = regexp_pattern($re_ref);

where C<$re_ref> is a reference to a compiled regular expression.  Upon
return, C<$mods> will be a string containing all the non-default
modifiers used when the regular expression was compiled, and C<$pattern>
the actual pattern.

If the actual stringification is important, or older Perls need to be
supported, you can use something like the following:

    # Accept both old and new-style stringification
    my $modifiers = (qr/foobar/ =~ /\Q(?^/) ? '^' : '-xism';

And then use C<$modifiers> instead of C<-xism>.

=head2 Regular expressions retain their localeness when interpolated

Regular expressions compiled under C<"use locale"> now retain this when
interpolated into a new regular expression compiled outside a
C<"use locale">, and vice-versa.

Previously, a regular expression interpolated into another one inherited
the localeness of the surrounding one, losing whatever state it
originally had.  This is considered a bug fix, but may trip up code that
has come to rely on the incorrect behavior.

=head2 Directory handles not copied to threads

On systems that do not have a C<fchdir> function, newly-created threads no
longer inherit directory handles from their parent threads. Such programs
would probably have crashed anyway
L<[perl #75154]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=75154>.

=head2 Negation treats strings differently from before

The unary negation operator C<-> now treats strings that look like numbers
as numbers
L<[perl #57706]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=57706>.

=head2 Negative zero

Negative zero (-0.0), when converted to a string, now becomes "0" on all
platforms. It used to become "-0" on some, but "0" on others.

If you still need to determine whether a zero is negative, use
C<sprintf("%g", $zero) =~ /^-/> or the L<Data::Float> module on CPAN.

=head1 Performance Enhancements

=over 4

=item *

The bulk of the C<Tie::Hash::NamedCapture> module used to be in the perl
core. It has now been moved to an XS module, to reduce the overhead for
programs that do not use C<%+> or C<%->.

=item *

Eliminate C<PL_*> accessor functions under ithreads.

When C<MULTIPLICITY> was first developed, and interpreter state moved into an
interpreter struct, thread and interpreter local C<PL_*> variables were defined
as macros that called accessor functions, returning the address of the value,
outside of the perl core. The intent was to allow members within the interpreter
struct to change size without breaking binary compatibility, so that bug fixes
could be merged to a maintenance branch that necessitated such a size change.

However, some non-core code defines C<PERL_CORE>, sometimes intentionally to
bypass this mechanism for speed reasons, sometimes for other reasons but with
the inadvertent side effect of bypassing this mechanism. As some of this code is
widespread in production use, the result is that the core B<can't> change the
size of members of the interpreter struct, as it will break such modules
compiled against a previous release on that maintenance branch. The upshot is
that this mechanism is redundant, and well-behaved code is penalised by
it. Hence it can and should be removed.

=back

=head1 Modules and Pragmata

=head2 Updated Modules and Pragmata

=over 4

=item *

C<Archive::Extract> has been upgraded from version 0.42 to 0.44

=item *

C<Carp> has been upgraded from version 1.18 to 1.19.

It no longer autovivifies the C<*CORE::GLOBAL::caller> glob, something it
started doing in 1.18, which was released with perl 5.13.4
L<[perl #78082]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=78082>

=item *

C<Compress::Raw::Bzip2> has been upgraded from version 2.030 to 2.031

Updated to use bzip2 1.0.6

=item *

C<CPAN> has been upgraded from version 1.94_57 to 1.94_61

=item *

C<Data::Dumper> has been upgraded from version 2.128 to 2.129.

C<Dumpxs> no longer crashes with globs returned by C<*$io_ref>
L<[perl #72332]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=72332>.

=item *

C<Digest::MD5> has been upgraded from version 2.40 to 2.51.

It is now safe to use this module in combination with threads.

=item *

C<File::DosGlob> has been upgraded from version 1.02 to 1.03.

It allows patterns containing literal parentheses (they no longer need to
be escaped). On Windows, it no longer adds an extra F<./> to the file names
returned when the pattern is a relative glob with a drive specification,
like F<c:*.pl>
L<[perl #71712]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=71712>.

=item *

C<File::Find> has been upgraded from version 1.17 to 1.18.

It improves handling of backslashes on Windows, so that paths such as
F<c:\dir\/file> are no longer generated
L<[perl #71710]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=71710>.

=item *

C<if> has been upgraded from version 0.05 to 0.06

=item *

C<IPC::Cmd> has been upgraded from version 0.60 to 0.64

=item *

C<IPC::Open3> has been upgraded from version 1.06 to 1.07.

The internal C<xclose> routine now knows how to handle file descriptors, as
documented, so duplicating STDIN in a child process using its file
descriptor now works
L<[perl #76474]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=71710>.

=item *

C<Locale::Codes> has been upgraded from version 3.13 to 3.14.

=item *

C<Locale::Maketext> has been upgraded from version 1.15 to 1.16.

It fixes an infinite loop in C<Locale::Maketext::Guts::_compile()> when
working with tainted values
(L<CPAN RT #40727|https://rt.cpan.org/Public/Bug/Display.html?id=40727>).

C<< ->maketext >> calls will now backup and restore C<$@> so that error
messages are not supressed
(L<CPAN RT #34182|https://rt.cpan.org/Public/Bug/Display.html?id=34182>).

=item *

C<Math::BigInt> has been upgraded from version 1.95 to 1.97.

This prevents C<sqrt($int)> from crashing under C<use bigrat;>
L<[perl #73534]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=73534>.

=item *

C<NEXT> has been upgraded from version 0.64 to 0.65.

=item *

C<overload> has been upgraded from version 1.10 to 1.11.

C<overload::Method> can now handle subroutines that are themselves blessed
into overloaded classes
L<[perl #71998]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=71998>.

=item *

C<PathTools> has been upgraded from version 3.31_01 to 3.34.

=item *

C<podlators> has been upgraded from version 2.3.1 to 2.4.0

=item *

C<sigtrap> has been upgraded from version 1.04 to 1.05.

It no longer tries to modify read-only arguments when generating a
backtrace
L<[perl #72340]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=72340>.

=item *

C<threads> has been upgraded from version 1.77_03 to 1.81_01.

=item *

C<threads::shared> has been upgrade from version 1.33_03 to 1.34

=item *

C<Unicode::Collate> has been upgraded from version 0.59 to 0.63

U::C::Locale newly supports locales: ar, be, bg, de__phonebook, hu, hy, kk, mk, nso, om, 
tn, vi, hr, ig, ru, sq, se, sr, to and uk

=item *

C<Unicode::Normalize> has been upgraded from version 1.06 to 1.07

=item *

C<B::Deparse> has been upgraded from version 0.98 to 0.99

B::Deparse now properly handles the code that applies a conditional
pattern match against implicit C<$_> as it was fixed in
L<[perl #20444]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=20444>.

=item *

C<GDBM_File> has been upgraded from version 1.10 to 1.11

=back

=head1 Documentation

=head2 Changes to Existing Documentation

=head3 L<perlapi>

=over 4

=item *

The documentation for the C<SvTRUE> macro was simply wrong in stating that
get-magic is not processed. It has been corrected.

=back

=head1 Diagnostics

The following additions or changes have been made to diagnostic output,
including warnings and fatal error messages.  For the complete list of
diagnostic messages, see L<perldiag>.

=head2 Changes to Existing Diagnostics

=over 4

=item *

The 'Layer does not match this perl' error message has been replaced with
these more helpful messages:

=over 4

=item *

PerlIO layer function table size (%d) does not match size expected by this
perl (%d)

=item *

PerlIO layer instance size (%d) does not match size expected by this perl
(%d)

=back

L<[perl #73754]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=73754>

=back

=head1 Testing

=over 4

=item *

The script F<t/op/threads-dirh.t> has been added, which tests interaction
of threads and directory handles.

=back

=head1 Platform Support

=head2 Platform-Specific Notes

=over 4

=item IRIX

Conversion of strings to floating-point numbers is now more accurate on
IRIX systems
L<[perl #32380]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=32380>.

=item Mac OS X

Early versions of Mac OS X (Darwin) had buggy implementations of the
C<setregid>, C<setreuid>, C<setrgid> and C<setruid> functions, so perl
would pretend they did not exist.

These functions are now recognised on Mac OS 10.5 (Leopard; Darwin 9) and
higher, as they have been fixed
L<[perl #72990]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=72990>.

=item OpenVOS

perl now builds again with OpenVOS (formerly known as Stratus VOS)
L<[perl #78132]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=78132>.

=item VMS

The shortening of symbols longer than 31 characters in the C sources is
now done by the compiler rather than by xsubpp (which could only do so
for generated symbols in XS code).

=item Windows

C<$Config{gccversion}> is now set correctly when perl is built using the
mingw64 compiler from L<http://mingw64.org>
L<[perl #73754]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=73754>.

The build process proceeds more smoothly with mingw and dmake when
F<C:\MSYS\bin> is in the PATH, due to a C<Cwd> fix.

=back

=head1 Internal Changes

=over 4

=item *

See L</Regular expressions retain their localeness when interpolated>,
above.

=item *

The C<sv_cmp_flags>, C<sv_cmp_locale_flags>, C<sv_eq_flags> and
C<sv_collxfrm_flags> functions have been added. These are like their
non-_flags counterparts, but allow one to specify whether get-magic is
processed.

The C<sv_cmp>, C<sv_cmp_locale>, C<sv_eq> and C<sv_collxfrm> functions have
been replaced with wrappers around the new functions. 

=item *

A new C<sv_2bool_flags> function has been added.

This is like C<sv_2bool>, but it lets the calling code decide whether
get-magic is handled. C<sv_2bool> is now a macro that calls the new
function.

=item *

A new macro, C<SvTRUE_nomg>, has been added.

This is like C<SvTRUE>, except that it does not process magic. It uses the
new C<sv_2bool_flags> function.

=item *

C<sv_catsv_flags> no longer calls C<mg_get> on its second argument (the
source string) if the flags passed to it do not include SV_GMAGIC. So it
now matches the documentation.

=item *

A new interface has been added for custom check hooks on subroutines. See
L</Custom per-subroutine check hooks>, above.

=item *

List op building functions have been added to the
API.  See L<op_append_elem|perlapi/op_append_elem>,
L<op_append_list|perlapi/op_append_list>, and
L<op_prepend_elem|perlapi/op_prepend_elem>.

=item *

The L<LINKLIST|perlapi/LINKLIST> macro, part of op building that
constructs the execution-order op chain, has been added to the API.

=item *

Many functions ending with pvn now have equivalent pv/pvs/sv versions.

=item *

The C<save_freeop>, C<save_op>, C<save_pushi32ptr> and C<save_pushptrptr>
functions have been added to the API.

=item *

The new API function C<parse_stmtseq()> parses a sequence of statements, up
to closing brace or EOF.

=back

=head1 Selected Bug Fixes

=over 4

=item *

A regular expression match in the right-hand side of a global substitution
(C<s///g>) that is in the same scope will no longer cause match variables
to have the wrong values on subsequent iterations. This can happen when an
array or hash subscript is interpolated in the right-hand side, as in
C<s|(.)|@a{ print($1), /./ }|g>
L<[perl #19078]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=19078>.

=item *

Constant-folding used to cause

  $text =~ ( 1 ? /phoo/ : /bear/)

to turn into

  $text =~ /phoo/

at compile time. Now it correctly matches against C<$_>
L<[perl #20444]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=20444>.

=item *

Parsing Perl code (either with string C<eval> or by loading modules) from
within a C<UNITCHECK> block no longer causes the interpreter to crash
L<[perl #70614]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=70614>.

=item *

When C<-d> is used on the shebang (C<#!>) line, the debugger now has access
to the lines of the main program. In the past, this sometimes worked and
sometimes did not, depending on what order things happened to be arranged
in memory
L<[perl #71806]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=71806>.

=item *

The C<y///> or C<tr///> operator now calls get-magic (e.g., the C<FETCH>
method of a tie) on its left-hand side just once, not twice
L<[perl #76814]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=76814>.

=item *

String comparison (C<eq>, C<ne>, C<lt>, C<gt>, C<le>, C<ge> and
C<cmp>) and logical not (C<not> and C<!>) operators no longer call magic
(e.g., tie methods) twice on their operands
L<[perl #76814]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=76814>.

This bug was introduced in an earlier 5.13 release, and does not affect
perl 5.12.

=item *

When a tied (or other magic) variable is used as, or in, a regular
expression, it no longer has its C<FETCH> method called twice
L<[perl #76814]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=76814>.

This bug was introduced in an earlier 5.13 release, and does not affect
perl 5.12.

=item *

The C<-C> command line option can now be followed by other options
L<[perl #72434]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=72434>.

=item *

Assigning a glob to a PVLV used to convert it to a plain string. Now it
works correctly, and a PVLV can hold a glob. This would happen when a
nonexistent hash or array element was passed to a subroutine:

  sub { $_[0] = *foo }->($hash{key});
  # $_[0] would have been the string "*main::foo"

It also happened when a glob was assigned to, or returned from, an element
of a tied array or hash
L<[perl #36051]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=36051>.

=item *

Creating a new thread when directory handles were open used to cause a
crash, because the handles were not cloned, but simply passed to the new
thread, resulting in a double free.

Now directory handles are cloned properly, on systems that have a C<fchdir>
function. On other systems, new threads simply do not inherit directory
handles from their parent threads
L<[perl #75154]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=75154>.

=item *

The regular expression parser no longer hangs when parsing C<\18> and
C<\88>.

This bug was introduced in version 5.13.5 and did not affect earlier
versions
L<[perl #78058]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=78058>.

=item *

Subroutine redefinition works once more in the debugger
L<[perl #48332]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=48332>.

=item *

The C<&> C<|> C<^> bitwise operators no longer coerce read-only arguments
L<[perl #20661]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=20661>.

=item *

Stringifying a scalar containing -0.0 no longer has the affect of turning
false into true
L<[perl #45133]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=45133>.

=item *

Aliasing packages by assigning to globs or deleting packages by deleting
their containing stash elements used to have erratic effects on method
resolution, because the internal 'isa' caches were not reset. This has been
fixed.

=item *

C<sort> with a custom sort routine could crash if too many nested
subroutine calls occurrred from within the sort routine
L<[perl #77930]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=77930>.

This bug was introduced in an earlier 5.13 release, and did not affect
perl 5.12.

=item *

The C<eval_sv> and C<eval_pv> C functions now set C<$@> correctly when
there is a syntax error and no C<G_KEEPERR> flag, and never set it if the
C<G_KEEPERR> flag is present 
L<[perl #3719]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=3719>.

=item *

Nested C<map> and C<grep> blocks no longer leak memory when processing
large lists
L<[perl #48004]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=48004>.

=item *

Malformed C<version> objects no longer cause crashes
L<[perl #78286]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=78286>.

=item *

The interpreter no longer crashes when freeing deeply-nested arrays of
arrays. Hashes have not been fixed yet
L<[perl #44225]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=44225>.

=item *

The mechanism for freeing objects in globs used to leave dangling
pointers to freed SVs, meaning Perl users could see corrupted state
during destruction.

Perl now only frees the affected slots of the GV, rather than freeing
the GV itself. This makes sure that there are no dangling refs or
corrupted state during destruction.

=item *

The typeglob C<*,>, which holds the scalar variable C<$,> (output field
separator), had the wrong reference count in child threads.

=item *

C<splice> now calls set-magic. This means that, for instance, changes made
by C<splice @ISA> are respected by method calls
L<[perl #78400]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=78400>.

=item *

C<use v5.8> no longer leaks memory
L<[perl #78436]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=78436>.

=item *

The XS multicall API no longer causes subroutines to lose reference counts
if called via the multicall interface from within those very subroutines.
This affects modules like List::Util. Calling one of its functions with an
active subroutine as the first argument could cause a crash
L<[perl #78070]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=78070>.

=back

=head1 Errata

=over 4

=item *

Fixed a typo in L<perl5135delta> regarding array slices and smart matching

=back

=head1 Acknowledgements

Perl 5.13.6 represents approximately one month of development since Perl
5.13.5 and contains 67920 lines of changes across 566 files from 47 authors
and committers:

A. Sinan Unur, Aaron Crane, Alex Davies, Ali Polatel, Allen Smith, Andrew Rodland,
Andy Dougherty, Ben Morrow, brian d foy, Casey West, Chip Salzenberg, Chris
'BinGOs' Williams, Craig A. Berry, David Golden, David Mitchell, Eric Brine,
Father Chrysostomos, Florian Ragwitz, George Greer, gregor herrmann, Jan Dubois,
Jerry D. Hedden, Jesse Vincent, Joshua Pritikin, Karl Williamson, kmx, Michael
G Schwern, Mike Kelly, Nicholas Clark, Paul Green, Rafael Garcia-Suarez, Renee
Baecker, Ricardo Signes, Sisyphus, Slaven Rezic, Steffen Müller, Steve Hay,
Sullivan Beck, Tatsuhiko Miyagawa, Todd Rinaldo, Tony Cook, Tye McQueen, Vernon
Lyon, Walt Mankowski, Zefram, Zsbán Ambrus, Ævar Arnfjörð Bjarmason.

Many of the changes included in this version originated in the CPAN
modules included in Perl's core. We're grateful to the entire CPAN
community for helping Perl to flourish.

=head1 Reporting Bugs

If you find what you think is a bug, you might check the articles
recently posted to the comp.lang.perl.misc newsgroup and the perl
bug database at http://rt.perl.org/perlbug/ .  There may also be
information at http://www.perl.org/ , the Perl Home Page.

If you believe you have an unreported bug, please run the B<perlbug>
program included with your release.  Be sure to trim your bug down
to a tiny but sufficient test case.  Your bug report, along with the
output of C<perl -V>, will be sent off to perlbug@perl.org to be
analysed by the Perl porting team.

If the bug you are reporting has security implications, which make it
inappropriate to send to a publicly archived mailing list, then please send
it to perl5-security-report@perl.org. This points to a closed subscription
unarchived mailing list, which includes all the core committers, who be able
to help assess the impact of issues, figure out a resolution, and help
co-ordinate the release of patches to mitigate or fix the problem across all
platforms on which Perl is supported. Please only use this address for
security issues in the Perl core, not for modules independently
distributed on CPAN.

=head1 SEE ALSO

The F<Changes> file for an explanation of how to view exhaustive details
on what changed.

The F<INSTALL> file for how to build Perl.

The F<README> file for general stuff.

The F<Artistic> and F<Copying> files for copyright information.

=cut