From: Nicholas Clark Date: Fri, 21 Jan 2011 09:26:24 +0000 (+0000) Subject: Remove training whitespace in Pod which can confuse pod/buildtoc X-Git-Tag: accepted/trunk/20130322.191538~5921 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=02f739158806d7975ddb99f2f4dc77cc4ff7be51;p=platform%2Fupstream%2Fperl.git Remove training whitespace in Pod which can confuse pod/buildtoc Some whitespace is being interpreted as "not a blank line" causing it (and possibly other parsers) to assume that subsequent text is part of the preceding =head or =item --- diff --git a/dist/Filter-Simple/lib/Filter/Simple.pm b/dist/Filter-Simple/lib/Filter/Simple.pm index 044dd54..2edd798 100644 --- a/dist/Filter-Simple/lib/Filter/Simple.pm +++ b/dist/Filter-Simple/lib/Filter/Simple.pm @@ -4,7 +4,7 @@ use Text::Balanced ':ALL'; use vars qw{ $VERSION @EXPORT }; -$VERSION = '0.85'; +$VERSION = '0.86'; use Filter::Util::Call; use Carp; @@ -609,7 +609,7 @@ with a final debugging pass that prints the resulting source code: =head2 Filtering only the code parts of source code - + Most source code ceases to be grammatically correct when it is broken up into the pieces between string literals and regexes. So the C<'code'> and C<'code_no_comments'> component filter behave slightly differently @@ -702,7 +702,7 @@ to install the filter: use Filter::Simple; FILTER { s/(\w+)/\U$1/ }; - + that will almost never be a problem, but if you install a filtering subroutine by passing it directly to the C statement: