Get perl5134delta into a mostly finished state

1 files changed, 34 insertions, 233 deletions

diff --git a/pod/perl5134delta.pod b/pod/perl5134delta.pod
index 596da1f530..e6533fa646 100644
--- a/pod/perl5134delta.pod
+++ b/pod/perl5134delta.pod
@@ -1,13 +1,7 @@
 =encoding utf8
 
-=for rafl
-changelogged up to commit 41f69a9
-
 =head1 NAME
 
-[ this is a template for a new perldelta file. Any text flagged as
-XXX needs to be processed before release. ]
-
 perldelta - what is new for perl v5.13.4
 
 =head1 DESCRIPTION
@@ -19,16 +13,8 @@ If you are upgrading from an earlier release such as 5.13.2, first read
 L<perl5133delta>, which describes differences between 5.13.2 and
 5.13.3.
 
-=head1 Notice
-
-XXX Any important notices here
-
 =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.
-
 =head2 C<srand()> now returns the seed
 
 This allows programs which need to have repeatable results to not have to come
@@ -83,14 +69,6 @@ C<\N{}>, C<charnames::vianame>, C<charnames::viacode> now know about every
 character in Unicode.  Previously, they didn't know about the Hangul syllables
 nor a number of CJK (Chinese/Japanese/Korean) characters.
 
-=head1 Security
-
-XXX Any security-related notices go here.  In particular, any security
-vulnerabilities closed should be noted here rather than in the
-L</Selected Bug Fixes> section.
-
-[ List each security issue as a =head2 entry ]
-
 =head1 Incompatible Changes
 
 =head2 Declare API incompatibility between blead releases
@@ -122,16 +100,10 @@ exception if they don't match.
 =head2 Binary Incompatible with all previous Perls
 
 Some bit fields have been reordered, hence this release will not be binary
-comptible with any previous Perl release.
+compatible with any previous Perl release.
 
 =head1 Deprecations
 
-XXX Any deprecated features, syntax, modules etc. should be listed here.
-In particular, deprecated modules should be listed here even if they are
-listed as an updated module in the L</Modules and Pragmata> section.
-
-[ List each deprecation as a =head2 entry ]
-
 =head2 List assignment to C<$[>
 
 After assignment to C<$[> has been deprecated and started to give warnings in
@@ -140,11 +112,6 @@ assigning to C<$[> in list context. This fixes an oversight in 5.12.0.
 
 =head1 Performance Enhancements
 
-XXX Changes which enhance performance without changing behaviour go here. There
-may well be none in a stable release.
-
-[ List each enhancement as a =item * entry ]
-
 =over 4
 
 =item *
@@ -163,8 +130,8 @@ platforms and configurations. On Win32, it's now about 100 times faster.
 =item *
 
 For weak references, the common case of just a single weak reference per
-referent has been optimised to reduce the storage required. In this case
-it saves the equivalent of one small perl array per referent.
+referent has been optimised to reduce the storage required. In this case it
+saves the equivalent of one small perl array per referent.
 
 =item *
 
@@ -175,25 +142,9 @@ they actually use, saving some space.
 
 =head1 Modules and Pragmata
 
-XXX All changes to installed files in F<cpan/>, F<dist/>, F<ext/> and F<lib/>
-go here.  If Module::CoreList is updated, generate an initial draft of the
-following sections using F<Porting/corelist-perldelta.pl>, which prints stub
-entries to STDOUT.  Results can be pasted in place of the '=head2' entries
-below.  A paragraph summary for important changes should then be added by hand.
-In an ideal world, dual-life modules would have a F<Changes> file that could be
-cribbed.
-
-[ Within each section, list entries as a =item NAME entry ]
-
 =head2 New Modules and Pragmata
 
-=over 4
-
-=item *
-
-XXX
-
-=back
+This release does not introduce any new modules or pragmata.
 
 =head2 Updated Modules and Pragmata
 
@@ -215,13 +166,12 @@ Upgraded from version 1.11 to 1.12.
 
 Upgraded from version 1.16 to 1.18.
 
-L<Carp> now detects incomplete L<caller()|perlfunc/"caller EXPR">
-overrides and avoids using bogus C<@DB::args>. To provide backtraces, Carp
-relies on particular behaviour of the caller built-in. Carp now detects
-if other code has overridden this with an incomplete implementation, and
-modifies its backtrace accordingly. Previously incomplete overrides would
-cause incorrect values in backtraces (best case), or obscure fatal errors
-(worst case)
+L<Carp> now detects incomplete L<caller()|perlfunc/"caller EXPR"> overrides and
+avoids using bogus C<@DB::args>. To provide backtraces, Carp relies on
+particular behaviour of the caller built-in. Carp now detects if other code has
+overridden this with an incomplete implementation, and modifies its backtrace
+accordingly. Previously incomplete overrides would cause incorrect values in
+backtraces (best case), or obscure fatal errors (worst case)
 
 This fixes certain cases of C<Bizarre copy of ARRAY> caused by modules
 overriding C<caller()> incorrectly.
@@ -240,7 +190,7 @@ Upgraded from version 3.31 to 3.31_01.
 
 Various issues in L<File::Spec::VMS> have been fixed.
 
-=item <I18N::Langinfo>
+=item C<I18N::Langinfo>
 
 Upgraded from version 0.03 to 0.04.
 
@@ -286,33 +236,12 @@ Upgraded from version 1.17 to 1.18.
 
 =head2 Removed Modules and Pragmata
 
-=over 4
-
-=item *
-
-XXX
-
-=back
+This release does not remove any modules or pragmata.
 
 =head1 Documentation
 
-XXX Changes to files in F<pod/> go here.  Consider grouping entries by
-file and be sure to link to the appropriate page, e.g. L<perlfunc>.
-
-=head2 New Documentation
-
-XXX Changes which create B<new> files in F<pod/> go here.
-
-=head3 L<XXX>
-
-XXX Description of the purpose of the new file here
-
 =head2 Changes to Existing Documentation
 
-XXX Changes which significantly change existing files in F<pod/> go here.
-However, any changes to F<pod/perldiag.pod> should go in the L</Diagnostics>
-section.
-
 =head3 L<perldiag>
 
 =over 4
@@ -376,69 +305,8 @@ Minor fix to a multiple scalar match example.
 
 =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>.
-
-XXX New or changed warnings emitted by the core's C<C> code go here. Also
-include any changes in L<perldiag> that reconcile it to the C<C> code.
-
-[ Within each section, list entries as a =item entry ]
-
-=head2 New Diagnostics
-
-XXX Newly added diagnostic messages go here
-
-=over 4
-
-=item *
-
-XXX
-
-=back
-
-=head2 Changes to Existing Diagnostics
-
-XXX Changes (i.e. rewording) of diagnostic messages go here
-
-=over 4
-
-=item *
-
-XXX
-
-=back
-
-=head1 Utility Changes
-
-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>.
-
-[ List utility changes as a =head3 entry for each utility and =item
-entries for each change
-Use L<XXX> with program names to get proper documentation linking. ]
-
-=head3 L<XXX>
-
-=over 4
-
-=item *
-
-XXX
-
-=back
-
 =head1 Configuration and Compilation
 
-XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
-go here.  Any other changes to the Perl build process should be listed here.
-However, any platform-specific changes should be listed in the
-L</Platform Support> section, instead.
-
-[ List changes as a =item entry ].
-
 =over 4
 
 =item *
@@ -454,14 +322,6 @@ default.
 
 =head1 Testing
 
-XXX Any significant changes to the testing of a freshly built perl should be
-listed here.  Changes which create B<new> files in F<t/> go here as do any
-large changes to the testing harness (e.g. when parallel testing was added).
-Changes to existing files in F<t/> aren't worth summarising, although the bugs
-that they represent may be covered elsewhere.
-
-[ List each test improvement as a =item entry ]
-
 =over 4
 
 =item *
@@ -487,45 +347,8 @@ L<Tie::ExtraHash> keeps working.
 
 =head1 Platform Support
 
-XXX Any changes to platform support should be listed in the sections below.
-
-[ Within the sections, list each platform as a =item entry with specific
-changes as paragraphs below it. ]
-
-=head2 New Platforms
-
-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.
-
-=over 4
-
-=item XXX-some-platform
-
-XXX
-
-=back
-
-=head2 Discontinued Platforms
-
-XXX List any platforms that this version of perl no longer compiles on.
-
-=over 4
-
-=item XXX-some-platform
-
-XXX
-
-=back
-
 =head2 Platform-Specific Notes
 
-XXX List any changes for specific platforms. This could include configuration
-and compilation changes or changes in portability/compatibility.  However,
-changes within modules for platforms should generally be listed in the
-L</Modules and Pragmata> section.
-
 =over 4
 
 =item Win32
@@ -538,7 +361,7 @@ Fixed a possible hang in F<t/op/readline.t>.
 
 =item *
 
-Fixed Makefile for SDK2003SP1 compilers.
+Fixed build process for SDK2003SP1 compilers.
 
 =item *
 
@@ -552,12 +375,6 @@ using new compilers, but for a perl compiled with old 32-bit compilers.
 
 =head1 Internal Changes
 
-XXX Changes which affect the interface available to C<XS> code go here.
-Other significant internal changes for future core maintainers should
-be noted as well.
-
-[ List each test improvement as a =item entry ]
-
 =over 4
 
 =item Removed C<PERL_POLLUTE>
@@ -573,7 +390,7 @@ conventions (and really should be completely obsolete by now).
 
 =item Added C<PERL_STATIC_INLINE>
 
-The C<PERL_STATIC_INLINE> define has been added to provide the buest-guess
+The C<PERL_STATIC_INLINE> define has been added to provide the best-guess
 incantation to use for static inline functions, if the C compiler supports
 C99-style static inline. If it doesn't, it'll give a plain C<static>.
 
@@ -584,12 +401,6 @@ inline functions.
 
 =head1 Selected Bug Fixes
 
-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>.
-
-[ List each fix as a =item entry ]
-
 =over 4
 
 =item *
@@ -641,15 +452,6 @@ Building with C<PERL_GLOBAL_STRUCT>, which has been broken accidentally in
 
 =head1 Known Problems
 
-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).
-
-This is a list of some significant unfixed bugs, which are regressions
-from either 5.XXX.XXX or 5.XXX.XXX.
-
-[ List each fix as a =item entry ]
-
 =over 4
 
 =item *
@@ -660,37 +462,36 @@ and will hopefully be released shortly.
 
 =back
 
-=head1 Obituary
+=head1 Acknowledgements
 
-XXX If any significant core contributor has died, we've added a short obituary
-here.
+Perl 5.13.4 represents approximately one month of development since Perl 5.13.3,
+and contains XXX lines of changes across XXX files from XXX authors and
+committers.
 
-=head1 Acknowledgements
+Thank you to the following for contributing to this release:
 
 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 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 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.
+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