In perl.git, the branch blead has been updated <http://perl5.git.perl.org/perl.git/commitdiff/e08634c5af6fd262ccfd6aab6b9ff9cbe1f2c897?hp=6156383d73f2f6524ee9ee99df53a43e80f8cd72>
- Log ----------------------------------------------------------------- commit e08634c5af6fd262ccfd6aab6b9ff9cbe1f2c897 Author: Steve Hay <[email protected]> Date: Mon Aug 13 09:18:45 2012 +0100 Minor perldelta changes including wrapping lines to 79 columns in the template pod. M Porting/perldelta_template.pod M pod/perldelta.pod commit 9c5f5e7ab30326bad0cf49befc2b1dce3fadb6dc Author: Steve Hay <[email protected]> Date: Mon Aug 13 08:55:31 2012 +0100 Begin editing perldelta for 5.17.3 Add list of modules upgraded so far, plus a few tidy-ups. M pod/perldelta.pod commit f293d8f7921776cefdcd78d97c3881b478aebc41 Author: Steve Hay <[email protected]> Date: Mon Aug 13 08:54:27 2012 +0100 Bump $Win32CORE::VERSION The .c file was changed by 2e94d7323a. M ext/Win32CORE/Win32CORE.pm ----------------------------------------------------------------------- Summary of changes: Porting/perldelta_template.pod | 101 ++++++++---------- ext/Win32CORE/Win32CORE.pm | 2 +- pod/perldelta.pod | 216 +++++++++++++++++++++++++--------------- 3 files changed, 180 insertions(+), 139 deletions(-) diff --git a/Porting/perldelta_template.pod b/Porting/perldelta_template.pod index d891614..6a8a8f0 100644 --- a/Porting/perldelta_template.pod +++ b/Porting/perldelta_template.pod @@ -2,19 +2,18 @@ =head1 NAME -[ this is a template for a new perldelta file. Any text flagged as -XXX needs to be processed before release. ] +[ 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.tXXX.cXXX =head1 DESCRIPTION -This document describes differences between the 5.sXXX.bXXX release and -the 5.tXXX.cXXX release. +This document describes differences between the 5.sXXX.bXXX release and the 5.tXXX.cXXX +release. If you are upgrading from an earlier release such as 5.rXXX.aXXX, first read -L<perl5XXXdelta>, which describes differences between 5.rXXX.aXXX and -5.sXXX.bXXX. +L<perl5XXXdelta>, which describes differences between 5.rXXX.aXXX and 5.sXXX.bXXX. =head1 Notice @@ -22,8 +21,8 @@ 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 +XXX New core language features go here. Summarize user-visible core language +enhancements. Particularly prominent performance optimisations could go here, but most should go in the L</Performance Enhancements> section. [ List each enhancement as a =head2 entry ] @@ -48,16 +47,16 @@ XXX For a release on a stable branch, this section aspires to be: =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. +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 ] =head1 Performance Enhancements -XXX Changes which enhance performance without changing behaviour go here. There -may well be none in a stable release. +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 ] @@ -97,7 +96,7 @@ XXX =item * -L<XXX> has been upgraded from version 0.69 to version 0.70. +L<XXX> has been upgraded from version A.xx to B.yy. =back @@ -146,20 +145,13 @@ 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 +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 that links to perldiag, - e.g. - - =item * - - L<Invalid version object|perldiag/"Invalid version object"> -] - =head2 New Diagnostics -XXX Newly added diagnostic messages go here +XXX Newly added diagnostic messages go under here, separated into New Errors +and New Warnings =head3 New Errors @@ -195,8 +187,8 @@ XXX Describe change here =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>. +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 @@ -234,7 +226,7 @@ XXX 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 +Changes to existing files in F<t/> aren't worth summarizing, although the bugs that they represent may be covered elsewhere. [ List each test improvement as a =item entry ] @@ -257,7 +249,7 @@ 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/> +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. @@ -283,7 +275,7 @@ XXX =head2 Platform-Specific Notes -XXX List any changes for specific platforms. This could include configuration +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. @@ -298,9 +290,9 @@ XXX =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. +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 change as a =item entry ] @@ -314,9 +306,8 @@ XXX =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>. +XXX Important bug fixes in the core language are summarized here. Bug fixes in +files in F<ext/> and F<lib/> are best summarized in L</Modules and Pragmata>. [ List each fix as a =item entry ] @@ -330,8 +321,8 @@ XXX =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. Unfixed +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. Unfixed platform specific bugs also go here. [ List each fix as a =item entry ] @@ -357,32 +348,30 @@ XXX Generate this with: =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 L<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 [email protected] to be -analysed by the Perl porting team. +If you believe you have an unreported bug, please run the L<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 [email protected] 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 [email protected]. This points to a closed subscription -unarchived mailing list, which includes -all the core committers, who will be able -to help assess the impact of issues, figure out a resolution, and help +inappropriate to send to a publicly archived mailing list, then please send it +to [email protected]. This points to a closed subscription +unarchived mailing list, which includes all the core committers, who will 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. +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<Changes> file for an explanation of how to view exhaustive details on +what changed. The F<INSTALL> file for how to build Perl. diff --git a/ext/Win32CORE/Win32CORE.pm b/ext/Win32CORE/Win32CORE.pm index 0e5d20b..f89bfab 100644 --- a/ext/Win32CORE/Win32CORE.pm +++ b/ext/Win32CORE/Win32CORE.pm @@ -1,6 +1,6 @@ package Win32CORE; -$VERSION = '0.02'; +$VERSION = '0.03'; # There is no reason to load this module explicitly. It will be # initialized using xs_init() when the interpreter is constructed. diff --git a/pod/perldelta.pod b/pod/perldelta.pod index b892511..1d2fe7d 100644 --- a/pod/perldelta.pod +++ b/pod/perldelta.pod @@ -2,19 +2,18 @@ =head1 NAME -[ this is a template for a new perldelta file. Any text flagged as -XXX needs to be processed before release. ] +[ 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.17.3 =head1 DESCRIPTION -This document describes differences between the 5.17.2 release and -the 5.17.3 release. +This document describes differences between the 5.17.2 release and the 5.17.3 +release. If you are upgrading from an earlier release such as 5.17.1, first read -L<perl5172delta>, which describes differences between 5.17.1 and -5.17.2. +L<perl5172delta>, which describes differences between 5.17.1 and 5.17.2. =head1 Notice @@ -22,8 +21,8 @@ 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 +XXX New core language features go here. Summarize user-visible core language +enhancements. Particularly prominent performance optimisations could go here, but most should go in the L</Performance Enhancements> section. [ List each enhancement as a =head2 entry ] @@ -57,29 +56,29 @@ versions of Perl, C<undef> was converted to the empty string. A value stored in an environment variable has always been stringified. In this release, it is converted to be only a byte string. First, it is forced to be a only a string. Then if the string is utf8 and the equivalent of -C<utf8::downgrade> works, that result is used; otherwise, the equivalent of -C<utf8::encode> is used, and a warning is issued about wide characters +C<utf8::downgrade()> works, that result is used; otherwise, the equivalent of +C<utf8::encode()> is used, and a warning is issued about wide characters (L</Diagnostics>). -=head2 C<given> now aliases the global $_ +=head2 C<given> now aliases the global C<$_> -Instead of assigning to an implicit lexical $_, C<given> now makes the -global $_ an alias for its argument, just like C<foreach>. However, it -still uses lexical $_ if there is lexical $_ in scope (again, just like +Instead of assigning to an implicit lexical C<$_>, C<given> now makes the +global C<$_> an alias for its argument, just like C<foreach>. However, it +still uses lexical C<$_> if there is lexical C<$_> in scope (again, just like C<foreach>). =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. +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 ] =head1 Performance Enhancements -XXX Changes which enhance performance without changing behaviour go here. There -may well be none in a stable release. +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 ] @@ -119,10 +118,14 @@ XXX =item * -L<B> has been upgraded from version 1.36 to version 1.37. All C<CVf_*> and -C<GVf_*> and more SV-related flag values are now provided as constants in -the C<B::> namespace and available for export. The default export list has -not changed. +L<B> has been upgraded from version 1.36 to 1.37. All C<CVf_*> and C<GVf_*> +and more SV-related flag values are now provided as constants in the C<B::> +namespace and available for export. The default export list has not changed. + +=item * + +L<B::Concise> has been upgraded from version 1.91 to 1.92. XXX Add change +notes. =item * @@ -131,14 +134,78 @@ loop controls with the correct precedence. =item * +L<Compress::Raw::Bzip2> has been upgraded from version 2.05201 to 2.055. XXX +Add change notes. + +=item * + +L<Compress::Raw::Zlib> has been upgraded from version 2.05401 to 2.056. XXX +Add change notes. + +=item * + +L<Data::Dumper> has been upgraded from version 2.135_06 to 2.135_07. It has +been optimized to only build a seen-scalar hash as necessary, thereby speeding +up serialization drastically. + +=item * + +L<Devel::Peek> has been upgraded from version 1.08 to 1.09. XXX Add change +notes. + +=item * + +L<Encode> has been upgraded from version 2.44 to 2.46. XXX Add change notes. + +=item * + +L<IO::Compress> has been upgraded from version 2.052 to 2.055. XXX Add change +notes. + +=item * + +L<Module::Build> has been upgraded from version 0.40 to 0.4002. XXX Add change +notes. + +=item * + +L<Module::CoreList> has been upgraded from version 2.69 to 2.70. XXX Add +change notes. + +=item * + +L<Module::Load::Conditional> has been upgraded from version 0.50 to 0.54. XXX +Add change notes. + +=item * + +L<Module::Metadata> has been upgraded from version 1.000009 to 1.000010. XXX +Add change notes. + +=item * + +L<re> has been upgraded from version 0.21 to 0.22. XXX Add change notes. + +=item * + L<Storable> has been upgraded from version 2.37 to 2.38. It can now freeze and thaw vstrings correctly. This causes a slight incompatible change in the storage format, so the format version has increased to 2.9. =item * -L<Data::Dumper> has been optimized to only build a seen-scalar has as -necessary, thereby speeding up serialization drastically. +L<Time::Local> has been upgraded from version 1.2000 to 1.2300. XXX Add change +notes. + +=item * + +L<Unicode::UCD> has been upgraded from version 0.44 to 0.45. XXX Add change +notes. + +=item * + +L<Win32CORE> has been upgraded from version 0.02 to 0.03. XXX Add change +notes. =back @@ -154,8 +221,8 @@ XXX =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>. +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 @@ -189,29 +256,13 @@ 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 +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 that links to perldiag, - e.g. - - =item * - - L<Invalid version object|perldiag/"Invalid version object"> -] - =head2 New Diagnostics -XXX Newly added diagnostic messages go here - -=over 4 - -=item * - -Attempts to put wide characters into environment variables via %ENV provoke -the warning "Wide character in setenv". - -=back +XXX Newly added diagnostic messages go under here, separated into New Errors +and New Warnings =head3 New Errors @@ -221,7 +272,8 @@ the warning "Wide character in setenv". L<Unterminated delimiter for here document|perldiag/"Unterminated delimiter for here document"> -This message now occurs when a here document label has an initial quotation mark but the final quotation mark is missing. +This message now occurs when a here document label has an initial quotation +mark but the final quotation mark is missing. This replaces a bogus and misleading error message about not finding the label itself [perl #114104]. @@ -234,7 +286,10 @@ label itself [perl #114104]. =item * -XXX L<message|perldiag/"message"> +L<Wide character in setenv|perldiag/"Wide character in setenv"> + +Attempts to put wide characters into environment variables via C<%ENV> now +provoke this warning. =back @@ -252,8 +307,8 @@ XXX Describe change here =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>. +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 @@ -291,7 +346,7 @@ XXX 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 +Changes to existing files in F<t/> aren't worth summarizing, although the bugs that they represent may be covered elsewhere. [ List each test improvement as a =item entry ] @@ -314,7 +369,7 @@ 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/> +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. @@ -340,7 +395,7 @@ XXX =head2 Platform-Specific Notes -XXX List any changes for specific platforms. This could include configuration +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. @@ -355,9 +410,9 @@ XXX =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. +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 change as a =item entry ] @@ -371,9 +426,8 @@ XXX =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>. +XXX Important bug fixes in the core language are summarized here. Bug fixes in +files in F<ext/> and F<lib/> are best summarized in L</Modules and Pragmata>. [ List each fix as a =item entry ] @@ -391,8 +445,8 @@ C<dump LABEL> no longer leaks its label. =item * -Constant folding no longer changes the behaviour of functions like C<stat> -and C<truncate> that can take either filenames or handles. +Constant folding no longer changes the behaviour of functions like C<stat()> +and C<truncate()> that can take either filenames or handles. C<stat 1 ? foo : bar> nows treats its argument as a file name (since it is an arbitrary expression), rather than the handle "foo". @@ -434,8 +488,8 @@ The C<ref> operator started leaking memory on blessed objects in Perl =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. Unfixed +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. Unfixed platform specific bugs also go here. [ List each fix as a =item entry ] @@ -461,32 +515,30 @@ XXX Generate this with: =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 L<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 [email protected] to be -analysed by the Perl porting team. +If you believe you have an unreported bug, please run the L<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 [email protected] 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 [email protected]. This points to a closed subscription -unarchived mailing list, which includes -all the core committers, who will be able -to help assess the impact of issues, figure out a resolution, and help +inappropriate to send to a publicly archived mailing list, then please send it +to [email protected]. This points to a closed subscription +unarchived mailing list, which includes all the core committers, who will 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. +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<Changes> file for an explanation of how to view exhaustive details on +what changed. The F<INSTALL> file for how to build Perl. -- Perl5 Master Repository
