Sunday 27th March 2011
Fedora Project
Updated perl-PPI 1.215 (general fix release) in Rawhide and F-15:
index_locations on an empty document no longer warns
- Corrected a bug in line-spanning attribute support
- Regression test for line-spanning attribute support
return { foo => 1 } should parse curlys as hash constructor, not block (CPAN RT#61305)
Fixed bug with map and regexp confusing PPI (CPAN RT#63943)
- Updated copyright year to 2011
Fix "bless {} probably contains a hash constructor" (CPAN RT#64247)
Backed out glob fix
Fix "cast can trump braces in PPI::Token::Symbol->symbol" (CPAN RT#65199)
Local Packages
Updated perl-Perl-Critic to 1.114, bumping the PPI version requirement to 1.215 and adding buildreq/req perl(Pod::Parser):
Documentation::RequirePodLinksIncludeText now handles nested POD formatting (CPAN RT#65569)
Clarified relation of severity numbers to names in Perl::Critic POD (CPAN RT#66017)
Removed caveats from Variables::RequireLocalizedPunctuationVars, no longer necessary with PPI 1.208 (CPAN RT#65514)
Have InputOutput::RequireBriefOpen attempt to expand scope as necessary to deal with the case where the open() and the corresponding close() are not in the same scope (CPAN RT#64437)
RegularExpressions::ProhibitUnusedCapture now looks inside double-quotish things (CPAN RT#38942)
RegularExpressions::ProhibitUnusedCapture now takes logical alternation into account, so that (e.g.)
if ( /(a)/ || /(b)/ ) { say $1; }
is not a violation (CPAN RT#38942)
ValuesAndExpressions::ProhibitCommaSeparatedStatements now recognizes 'return { foo => 1, bar => 2 }' as containing a hash constructor, not a block; this was fixed by PPI 1.215 (CPAN RT#61301)
ValuesAndExpressions::ProhibitCommaSeparatedStatements now recognizes 'bless { foo => 1, bar => 2 }' as containing a hash constructor, not a block; this was fixed by PPI 1.215 (CPAN RT#64132)
Updated c-ares so that the %description of the devel package no longer mentions static libraries, which haven't been included for a very long time; I emailed the Fedora maintainer about this issue and the next build of the Fedora package will contain the same fix