Pod::Parser was warning that empty lines using DOS newlines are a
"line containing nothing but whitespace". Just run pod2man on
perldos.pod to watch the fun.
The following is a minor correction so it reconizes both "\015" and
"\012\015" as empty, blank lines. I don't know if you want to adjust it
for the OS.
FYI Mac newlines (\015) are dealt with correctly.
--- lib/Pod/Parser.pm 2000/03/03 22:43:41
+++ lib/Pod/Parser.pm 2000/03/03 23:01:26
@@ -1063,8 +1063,9 @@
## If it isnt, then keep iterating until it is.
next unless (($textline =~ /^(\s*)$/) && (length $paragraph));
- ## Issue a warning about any non-empty blank lines
- if (length($1) > 1 and ! $self->{_CUTTING}) {
+ ## Issue a warning about any non-empty blank lines, careful about
+ ## DOS newlines.
+ if ((length($1) > 1 and $1 ne "\015\012") and ! $self->{_CUTTING}) {
my $errorsub = $self->errorsub();
my $file = $self->input_file();
$file = VMS::Filespec::unixify($file) if $^O eq 'VMS';
An alternate approach would be to simply check if $1 eq "\n" allowing
it to adjust itself on a per OS basis. I don't think this is
desireble since I have perldos.pod installed on my machine with DOS
newlines even though I'm on a Unix machine and I don't like to see the
spew of warnings from pod2man. Also, since 5.6 code should handle
foreign newlines quietly, there's no reason the POD parsers shouldn't
do the same.
--
Michael G. Schwern <[EMAIL PROTECTED]> http://www.pobox.com/~schwern/
Plus I remember being impressed with Ada because you could write an
infinite loop without a faked up condition. The idea being that in Ada
the typical infinite loop would be normally be terminated by detonation.
-- Larry Wall in <[EMAIL PROTECTED]>
