=head1 NAME
-[ Any text flagged as XXX needs to be processed before release. ]
-
-perldelta - what is new for perl v5.11.1
+perl5111delta - what is new for perl v5.11.1
=head1 DESCRIPTION
This document describes differences between the 5.11.0 release and
the 5.11.1 release.
-=head1 Notice
-
-XXX Notice
-
=head1 Incompatible Changes
-XXX For a release on a stable branch, this section aspires to be:
-
- There are no changes intentionally incompatible with 5.XXX.XXX. If any
- exist, they are bugs and reports are welcome.
-
-
-=head1 Core Enhancements
-
-XXX New core language features go here. Summarise user-visible core language
-enhancements. Particularly prominent performance optimisations could go
-here, but most should go in the L</Performance Enhancements> section.
+=over
-=head1 New Platforms
+=item *
-XXX List any platforms that this version of perl compiles on, that previous
-versions did not. These will either be enabled by new files in the F<hints/>
-directories, or new subdirectories and F<README> files at the top level of the
-source tree.
+The boolkeys op moved to the group of hash ops. This breaks binary compatibility.
-=head1 Modules and Pragmata
-
-XXX All changes to installed files in F<ext/> and F<lib/> go here, in a list
-ordered by distribution name. Minimally it should be the module version,
-but it's more useful to the end user to give a paragraph's summary of the
-module's changes. In an ideal world, dual-life modules would have a
-F<Changes> file that could be cribbed.
+=item *
-=head2 New Modules and Pragmata
+C<\s> C<\w> and C<\d> once again have the semantics they had in Perl 5.8.x.
-=over 4
-=item C<XXX>
+=back
-XXX
+=head1 Core Enhancements
-=back
+=head2 Add C<package NAME VERSION> syntax
-=head2 Pragmata Changes
+This new syntax allows a module author to set the $VERSION of a namespace
+when the namespace is declared with 'package'. It eliminates the need
+for C<our $VERSION = ...> and similar constructs. E.g.
-=over 4
+ package Foo::Bar 1.23;
+ # $Foo::Bar::VERSION == 1.23
-=item C<XXX>
+There are several advantages to this:
-XXX
+=over
-=back
+=item *
-=head2 Updated Modules
+C<$VERSION> is parsed in I<exactly> the same way as C<use NAME VERSION>
-=over 4
+=item *
-=item C<XXX>
+C<$VERSION> is set at compile time
-XXX
+=item *
-=back
+Eliminates C<$VERSION = ...> and C<eval $VERSION> clutter
-=head1 Utility Changes
+=item *
-XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go
-here. Most of these are built within the directories F<utils> and F<x2p>.
+As it requires VERSION to be a numeric literal or v-string
+literal, it can be statically parsed by toolchain modules
+without C<eval> the way MM-E<gt>parse_version does for C<$VERSION = ...>
-=over 4
+=item *
-=item F<XXX>
+Alpha versions with underscores do not need to be quoted; static
+parsing will preserve the underscore, but during compilation, Perl
+will remove underscores as it does for all numeric literals
-XXX
+It does not break old code with only C<package NAME>, but code that uses
+C<package NAME VERSION> will need to be restricted to perl 5.11.X or newer
+This is analogous to the change to C<open> from two-args to three-args.
+Users requiring the latest Perl will benefit, and perhaps N years from
+now it will become standard practice when Perl 5.12 is targeted the way
+that 5.6 is today.
=back
-=head1 New Documentation
-
-XXX Changes which create B<new> files in F<pod/> go here.
+=head1 Modules and Pragmata
-=over 4
+=head2 Updated Modules
-=item L<XXX>
+=over 4
-XXX
+=item *
-=back
+Upgrade to Test-Simple 0.94
-=head1 Changes to Existing Documentation
+=item *
-XXX Changes which significantly change existing files in F<pod/> go here.
-Any changes to F<pod/perldiag.pod> should go in L</New or Changed Diagnostics>.
+Upgrade to Storable 2.21
+=item *
-=head1 Performance Enhancements
+Upgrade to Pod-Simple 3.08
-XXX Changes which enhance performance without changing behaviour go here. There
-may well be none in a stable release.
+=item *
-=over 4
+Upgrade to Parse-CPAN-Meta 1.40
=item *
-XXX
-
-=back
+Upgrade to ExtUtils-Manifest 1.57
-=head1 Installation and Configuration Improvements
+=item *
-XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
-go here.
+Upgrade to ExtUtils-CBuilder 0.260301
-=head2 Configuration improvements
+=item *
-XXX
+Upgrade to CGI.pm-3.48
-=head2 Compilation improvements
+=item *
-XXX
+Upgrade CPANPLUS to CPAN version 0.89_02
-=head2 Platform Specific Changes
+=item *
-=over 4
+Upgrade to threads::shared 1.32
-=item XXX-some-platform
+=item *
-XXX
+Upgrade ExtUtils::ParseXS to 2.21
-=back
+=item *
-=head1 Selected Bug Fixes
+Upgrade File::Path to 2.08 (and add taint.t test)
-XXX Important bug fixes in the core language are summarised here.
-Bug fixes in files in F<ext/> and F<lib/> are best summarised in
-L</Modules and Pragmata>.
+=item *
-=over 4
+Upgrade Module::CoreList to 2.20
=item *
-XXX
+Updated Object::Accessor to0.36
=back
-=head1 New or Changed Diagnostics
-
-XXX New or changed warnings emitted by the core's C<C> code go here.
+=head1 New Documentation
=over 4
-=item C<XXX>
+=item *
-XXX
+L<perlpolicy> extends the "Social contract about contributed modules" into
+the beginnings of a document on Perl porting policies.
=back
-=head1 Changed Internals
-
-XXX Changes which affect the interface available to C<XS> code go here.
-
-=over 4
+=head1 Changes to Existing Documentation
-=item *
+=over
-XXX
+=item Documentation for C<$1> in perlvar.pod clarified
=back
-=head1 Testing
-
-XXX Changes which create B<new> files in F<t/> go here. Changes to
-existing files in F<t/> aren't worth summarising, although the bugs that
-they represent may be.
+=head1 Performance Enhancements
=over 4
-=item Significant cleanups to core tests to ensure that language and interpreter features are not used before they're tested.
-
-XXX
+=item C<if (%foo)> has been optimized to be faster than C<if (keys %foo)>
=back
-=head1 Known Problems
+=head1 Platform Specific Notes
-XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
-tests that had to be C<TODO>ed for the release would be noted here, unless
-they were specific to a particular platform (see below).
+=over 4
-This is a list of some significant unfixed bugs, which are regressions
-from either 5.10.1 or 5.11.0.
+=item Darwin (Mac OS X)
=over 4
=item *
-XXX
+Skip testing the be_BY.CP1131 locale on Darwin 10 (Mac OS X 10.6),
+as it's still buggy.
-=back
+=item *
-=head1 Deprecations
+Correct infelicities in the regexp used to identify buggy locales
+on Darwin 8 and 9 (Mac OS X 10.4 and 10.5, respectively).
-XXX Add any new known deprecations here.
+=back
-The following items are now deprecated.
+=item DragonFly BSD
=over 4
=item *
-XXX
+Fix thread library selection [perl #69686]
=back
-=head1 Platform Specific Notes
-
-XXX Any changes specific to a particular platform. VMS and Win32 are the usual
-stars here. It's probably best to group changes under the same section layout
-as the main perldelta
-
-
-=head1 Obituary
-
-XXX If any significant core contributor has died, we've added a short obituary
-here.
-
-=head1 Acknowledgements
-
-XXX The list of people to thank goes here.
-
-
-=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
-
-This is all changes through 704e1b1e
-
-
- Update CPANPLUS to CPAN version 0.89_02
+=item Win32
- Upgrade to threads::shared 1.32
-
- Help ExtUtils::Install's tests find PERL_SRC on VMS.
-
-commit d1d15184c41c6ad4f16829561163cd118e5ae917
-Author: Nicholas Clark <nick@ccl4.org>
-Date: Tue Oct 13 16:04:18 2009 +0100
-
- Enable deprecation warnings by default.
-
- locked is deprecated, so use :lvalue instead.
-
- Can't use C<shift INC> to avoid @ in a commandline now, so use eval and octal.
-
- shift with barewords is deprecated, so this test from perl 1 needs updating.
-
- push and pop on barewords are deprecated, so need no warnings 'deprecated';
-
- Opening dirhandle DIR also as a file needs no warnings 'deprecated';
-
- defined @array and defined %hash need no warnings 'deprecated';
-
- localisation of $[ is deprecated, so needs no warnings 'deprecated';
-
- Tests for barewords and hash operators need no warnings 'deprecated';
-
- do subname() is deprecated, so tests for it need no warnings 'deprecated';
-
- Bracket deprecated features with no warnings 'deprecated';
-
- Move the test for the deprecated feature <<; out of t/base/lext.t
-
- Tests in base can't utilise pragmata, specifically no warnings 'deprecated';
-
- Add no warnings 'deprecated' to a test that assigns to $[
-
-commit a44d0896a6c4bfe01ea532694b8c1c073ea6a2f1
-Author: Nicholas Clark <nick@ccl4.org>
-Date: Thu Oct 15 23:37:41 2009 +0100
-
- Skip testing the be_BY.CP1131 locale on Darwin 10, as it's still buggy.
-
- Correct infelicities in the regexp used to identify buggy locales on Darwin 8
- and 9.
-
- POSIX::strftime() should be able to handle Unicode characters in the format
- string.
-
-commit 2e0eeeaafce11cb0128a6d1e245f1a5b806e3a87
-Author: Nicholas Clark <nick@ccl4.org>
-Date: Thu Oct 15 15:12:49 2009 +0100
-
- Move the boolkeys op to the group of hash ops.
-
- This breaks binary compatibility.
-
-commit 867fa1e2da145229b4db2c6e8d5b51700c15f114
-Author: demerphq <demerphq@gmail.com>
-Date: Thu Oct 15 14:27:30 2009 +0100
-
- Optimise if (%foo) to be faster than if(keys %foo)
-
- Thread was "[PATCH] Make if (%hash) {} act the same as if (keys %hash) {}"
- http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-11/msg00432.html
- but the implementation evolved from the approach described in the subject, to
- instead add a new opcode pp_boolkeys, to exactly preserve the existing
- behaviour.
-
- Various conflicts with the passage of time resolved, 'register' removed, and a
- $VERSION bump.
-
-commit 1c85afcecc8ee030e2780aa5bfa85692c8db64df
-Author: demerphq <demerphq@gmail.com>
-Date: Thu Oct 15 14:22:47 2009 +0100
-
- Support for pp_boolkeys in B::Deparse.
-
- Part of "[PATCH] Make if (%hash) {} act the same as if (keys %hash) {}"
- http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-11/msg00432.html
- which evolved from the approach described in the subject, to instead add a new
- opcode pp_boolkeys, to exactly preserve the existing behaviour.
-
- Plus a $VERSION bump.
-
-commit 55b77936aef50881a71470fd06e66edffd66d9de
-Author: Sisyphus <sisyphus1@optusnet.com.au>
-Date: Wed Oct 14 10:02:16 2009 -0400
-
- Add mingw64 support for win32
-
-commit d4c22fec77d7244882ce42a93a4ad25bdada2519
-Author: Sisyphus <sisyphus1@optusnet.com.au>
-Date: Wed Oct 14 06:58:49 2009 -0400
-
- Patch t/win32/system.t for mingw32/64
-
-commit e4d771f5006ebd70b76422437cce60e9ac40c830
-Author: Jan Dubois <jand@activestate.com>
-Date: Tue Oct 13 16:46:58 2009 -0700
-
- The winsock select() implementation doesn't support all empty 'fd_set's.
-
- The code already contained a workaround for the special case
-
- select(undef, undef, undef, $sleep);
-
- but didn't handle the case when actual bit vectors were passed in
- that didn't have any bits set.
-
- Fixes http://rt.perl.org/rt3/Public/Bug/Display.html?id=54544
-
-
-
-
-
-
- Podify the social contract about contributed module. Turn it into a policy document. Move the new "perl policy" document into pod/
-
-
-Author: Smylers <Smylers@stripey.com>
-Date: Tue Oct 13 14:14:46 2009 +0200
-
- perlvar $1 clarification
-
- $1 is currently documented as being set by the "last pattern match".
- But it is left alone by unsuccessful pattern match attempts (continuing
- to hold a value from an earlier successful match).
-
- Saying "last successful pattern match" clarifies this; it's also the
- phrase used to document $&.
-
- Second, the entry for $1 in perlvar doesn't actually contain the text
- "$1" anywhere. As such, doing man perlvar then using /\$1 to search for
- it in less doesn't locate it (though does match other places in that
- file where $1 happens to be used).
-
-
- =item *
-
- Replace Perl_deprecate() with a macro that calls Perl_ck_warner()
- Perl_deprecate was not part of the public API, and did not have a deprecate()
- shortcut macro defined without -DPERL_CORE. Neither codesearch.google.com nor
- CPAN::Unpack show any users outside the core.
-
-
-
- =item *
- Remove category 'syntax' from 5 warnings that should just be in 'deprecated'.
-
- None were documented as also being in 'syntax'. Effectively, this completes the
- reorganisation of commits 12bcd1a617c74d6e and 9014280dc8264580. See
- http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2009-10/msg00601.html and
- http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2002-03/msg00850.html
+=over 4
+=item *
+Initial support for mingw64 is now available
-commit c989e6a3e4b89b26d315693449c76cdcb754611f
-Author: Geoffrey T. Dairiki <dairiki at dairiki.org>
-Date: Tue Aug 4 17:54:34 2009 -0700
+=item *
- overload no longer implicitly unsets fallback on repeated 'use overload' lines - Fix for RT#68916
+Various bits of Perl's build infrastructure are no longer converted to win32 line endings at release time. If this hurts you, please speak up.
+=back
-commit 5f5991a0d6d8ef99d2643b88a7d9285e35277331
-Author: Nicholas Clark <nick@ccl4.org>
-Date: Mon Oct 12 15:54:30 2009 +0100
- Normalise 3 fatal pack/unpack error messages to "panic: %s"
+=back
-commit 04e82a462b85b3d6265b04aa07a405316616dc66
-Author: Nicholas Clark <nick@ccl4.org>
-Date: Sun Oct 11 18:56:01 2009 +0100
+=head1 Selected Bug Fixes
- porting/manifest.t now tests that all files listed in MANIFEST are present.
+=over 4
-commit 41239ce77fcd273e18c4017d3d96a5f42e228594
-Author: Nicholas Clark <nick@ccl4.org>
-Date: Sun Oct 11 17:28:02 2009 +0100
+=item *
- Default to running tests in cpan/ with relative paths for perl and @INC
+Perl now properly returns a syntax error instead of segfaulting
+if C<each>, C<keys> or C<values> is used without an argument
- Explicitly turn paths absolute for the 33 extensions in cpan/ that fail tests
- with relative paths.
+=item *
-commit fc5e5837c991d3d3224259ff5c1d728d4e0636e2
-Author: Nicholas Clark <nick@ccl4.org>
-Date: Sun Oct 11 15:05:58 2009 +0100
+C<tell()> now fails properly if called without an argument and when no previous file was read
- MakeMaker::Test::Utils::perl_lib now copes with relative paths for core testing.
+C<tell()> now returns C<-1>, and sets errno to C<EBADF>, thus restoring the 5.8.x behaviour
- In the core, @INC already contains the moral equivalent of blib/lib. However,
- it's a relative path (by default), so make it absolute. It's easier to KISS if
- this is done *before* any change of directory, so document this, and change the
- non-core case to add the absolute path of 'blib/lib' to @INC, rather than the
- absolute path of '../blib/lib'.
+=item *
+overload no longer implicitly unsets fallback on repeated 'use overload' lines
- Upgrade to Test-Simple-0.94
+=item *
- Upgrade to Storable-2.21
+POSIX::strftime() can now handle Unicode characters in the format string.
- Upgrade to Pod-Simple-3.08
+=item *
- Upgrade to Parse-CPAN-Meta-1.40
+The Windows select() implementation now supports all empty C<fd_set>s more correctly.
- Upgrade to ExtUtils-Manifest-1.57
+=back
- Upgrade to ExtUtils-CBuilder-0.260301
+=head1 New or Changed Diagnostics
+=over 4
- Upgrade to CGI.pm-3.48
-commit 6c1b5ced18901286f16f6d5f6914ba4b5e3db601
-Author: Simon 'corecode' Schubert <corecode@fs.ei.tum.de>
-Date: Sat Oct 10 17:55:26 2009 +0100
+=item *
- [perl #69686] Fix DragonFly thread lib selection
+The 'syntax' category was removed from 5 warnings that should only be in 'deprecated'.
+=item *
+Three fatal pack/unpack error messages have been normalized to "panic: %s"
-Merge: 8e32470 e92f586
-Author: Rafael Garcia-Suarez <rgs@consttype.org>
-Date: Thu Oct 8 15:13:18 2009 +0200
+=item *
- Merge branch 'feature/package-name-version' into blead
+"Unicode character is illegal" has been rephrased to be more accurate
-commit f03173f2c707a804ec3e9c291d2ab1adb9db4abc
-Author: Rafael Garcia-Suarez <rgs@consttype.org>
-Date: Thu Oct 8 11:44:21 2009 +0200
+It now reads C<Unicode non-character is illegal in interchange> and the
+perldiag documentation has been expanded a bit.
- Make tell() fail properly if called without an argument and when no previous file was read
+=item *
- This makes tell() return -1, and sets errno to EBADF, thus
- restoring the 5.8.x behaviour
+Perl now defaults to issuing a warning if a deprecated language feature is used.
-commit a916b30221d5aac718ed67c9a5bc9c0905daddd0
-Author: Rafael Garcia-Suarez <rgs@consttype.org>
-Date: Thu Oct 8 11:33:06 2009 +0200
+To disable this feature in a given lexical scope, you should use C<no
+warnings 'deprecated';> For information about which language features
+are deprecated and explanations of various deprecation warnings, please
+see L<perldiag>
- Properly return a syntax error instead of segfaulting if each/keys/values is used without an argument
+=back
- =item Updated Object-Accessor to CPAN version 0.36
+=head1 Testing
+=over 4
- Add perltodo: write an XS cookbook
+=item *
- Porting/checkAUTHORS.pl now runs clean
+Significant cleanups to core tests to ensure that language and
+interpreter features are not used before they're tested.
-commit 6fa4d285bff5644bebb95aff09143322042282cc
-Author: David Golden <dagolden@cpan.org>
-Date: Tue Oct 6 06:48:48 2009 -0400
+=item *
- Add 'package NAME VERSION' syntax
+C<make test_porting> now runs a number of important pre-commit checks which might be of use to anyone working on the Perl core.
- This patch adds support for setting the $VERSION of a namespace
- when the namespace is declared with 'package'. It eliminates the
- need for 'our $VERSION = ...' and similar constructs. E.g.
+=item *
- package Foo::Bar 1.23;
- # $Foo::Bar::VERSION == 1.23
+F<t/porting/podcheck.t> automatically checks the well-formedness of
+POD found in all .pl, .pm and .pod files in the F<MANIFEST>, other than in
+dual-lifed modules which are primarily maintained outside the Perl core.
- There are several advantages to this:
+=item *
- * VERSION is parsed in *exactly* the same way as 'use NAME VERSION'
+F<t/porting/manifest.t> now tests that all files listed in MANIFEST are present.
- * $VERSION is set at compile time
+=back
- * Eliminates '$VERSION = ...' and 'eval $VERSION' clutter
+=head1 Known Problems
- * As it requires VERSION to be a numeric literal or v-string
- literal, it can be statically parsed by toolchain modules
- without 'eval' the way MM->parse_version does for '$VERSION = ...'
+=over 4
- * Alpha versions with underscores do not need to be quoted; static
- parsing will preserve the underscore, but during compilation, Perl
- will remove underscores as it does for all numeric literals
+=item Untriaged test crashes on Windows 2000
- During development of this, there was discussion on #corehackers and
- elsewhere that this should also allow other metadata to be set such as
- "status" (stable/alpha) or "author/authority". On reflection, those
- metadata are not very well defined yet and likely should never be
- encoded into Perl core parsing so they can be freely changed in the
- future. (They could perhaps be achieved via a comment on the same line
- as 'package NAME VERSION'.)
+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.
- Version numbers, however, already have a very specific definition and
- use defined in the core through 'use NAME VERSION'. This patch merely
- provides appropriate symmetry for setting $VERSION with the exact same
- parsing and semantics as 'use'.
+=item Known test failures on VMS
- It does not break old code with only 'package NAME', but code that
- uses 'package NAME VERSION' will need to be restricted to perl 5.11.X.
- This is analogous to the change to open() from two-args to three-args.
- Users requiring the latest Perl will benefit, and perhaps N years from
- now it will become standard practice when Perl 5.12 is targeted the
- way that 5.6 is today.
+Perl 5.11.1 fails a small set of core and CPAN tests as of this release.
+With luck, that'll be sorted out for 5.11.2
- The patch does not prevent 'package NAME VERSION' from being used
- multiple times for the same package with different version numbers, but
- nothing prevents $VERSION from being modified arbitrarily at runtime,
- either, so I see no urgen reason to add limitations or warnings so
- long as Perl uses a global $VERSION variable for package version
- numbers.
+=back
- I am posting this patch to the p5p list for discussion and review. If
- there seems to be general assent (or lack of dissent), I will go ahead
- and commit the patch to blead.
+=head1 Errata for 5.11.0
-commit a67b1afafddaaed84e79a867acc888c9ccfb6460
-Author: Max Maischein <corion@corion.net>
-Date: Mon Oct 5 22:49:09 2009 +0200
+=over
-New porting tests to automatically check POD in lib/, ext/ and pod/
+=item The Perl 5.11.0 release notes incorrectly described 'delete local'
-commit 2d5f1d01166a325b29ccc86102d26e68def13786
-Author: David Golden <dagolden@cpan.org>
-Date: Mon Oct 5 17:46:36 2009 -0400
+=back
- Explain using git send-email for patches
+=head1 Acknowledgements
- =item Update ExtUtils::ParseXS to 2.21
+Perl 5.11.1 represents approximately 3 weeks development since Perl 5.11.0
+contains 22,000 lines of changes across 396 files from 26 authors and committers:
- =item Upgrade File::Path to 2.08 (and add taint.t test)
+Abigail, Alex Vandiver, brian d foy, Chris Williams, Craig A. Berry,
+David Fifield, David Golden, demerphq, Eric Brine, Geoffrey T. Dairiki,
+George Greer, H.Merijn Brand, Jan Dubois, Jerry D. Hedden, Jesse Vincent,
+Josh ben Jore, Max Maischein, Nicholas Clark, Rafael Garcia-Suarez,
+Simon Schubert, Sisyphus, Smylers, Steve Hay, Steve Peters, Vincent Pit
+and Yves Orton.
-commit b2680017d861a93d2d51b07bce2f1731086bc8c3
-Author: Yves Orton <demerphq@gmail.com>
-Date: Mon Oct 5 09:34:52 2009 +0200
+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.
- in regexec.c move the BOUND logic out of the way of the special CC logic
+=head1 Reporting Bugs
- This is a first step towards macroizing the special CC handler logic so
- it is easier to maintain them, for instance interestng optimisations are
- being used in one, but not all, even though the logic is sharable. By
- moving the BOUND logic out of the way the code repition is much clearer.
+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.
-commit e74a3e73f5e128a77b691fcfc83214f58419a493
-Author: Jesse Vincent <jesse@bestpractical.com>
-Date: Sun Oct 4 05:22:17 2009 +0900
+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.
- Correcting mistaken description of 'delete local' in perl5110delta
+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.
- Reported by nothingmuch++ and rjbs++
+=head1 SEE ALSO
- =TODO FOR RELENG GUIDE Make Module::Corelist recognise $] as a version number on 5.11.0
+The F<Changes> file for an explanation of how to view exhaustive details
+on what changed.
- =item Bump version to 2.20
+The F<INSTALL> file for how to build Perl.
-commit 6f6ac1dea8501596050bc974dc468632797d51eb
-Author: Rafael Garcia-Suarez <rgs@consttype.org>
-Date: Sat Oct 3 09:56:42 2009 +0200
+The F<README> file for general stuff.
- Change warning "Unicode character is illegal" to more accurate description
+The F<Artistic> and F<Copying> files for copyright information.
- That now reads "Unicode non-character is illegal in interchange" and the
- perldiag documentation is expanded a bit.
+=cut