I have uploaded the beta for a new version of PodParser to my own personal FTP site at: ftp://ftp.enteract.com/users/bradapp/src/libs/Perl/PodParser-1.093.tar.gz Changes are as follows: ======================= + added mandatory warning for non-empty blank lines matching /^\s+$/ + got rid of special handling of '=>' and '=>' inside C<..> and instead implemented the more general rules posted by Larry Wall on P5P allowing /[A-Z]<...>/ and /[A-Z]<[<:]\s+...\s+[:>]>/ to deal with things like embedded '->' and '=>' using whitespace, as in: C<< <=> >> and I<< <> >>. + added proposals by Wolfgang Laun to Pod::Checker + more tweaks to ParseUtils.pm by Marek Rouchal The only reason this is a *beta* release is because this version implements the C<< $a <=> $b >> syntax which changes the current definition of perlpod.pod *and* changes some existing behavior and breaks a handful of existing pods that took advantage of previous special-handling of '->' and '=>' inside of C<...>. The new parsing behavior is a result of consensus (and apparent approval from Larry) of changing the old behavior into the new behavior and functionality. My question is whether or not the new C<< ... >> functionality can reasonably go into Perl5.6 because of: * mods to existing pods that may now be broken * mods to perlpod.pod that translators using Pod::Parser can now understand but which modules that do not (like pod2html) do not. If I need to temporarily disable the new functionality and reinstate the old for the purpose of Perl5.6, please let me know ASAP and I will do so. -- Brad Appleton <bradapp@enteract.com> http://www.enteract.com/~bradapp/ "And miles to go before I sleep." -- Robert Frost