comment on

Thanks Rob!

I'm on 32 bit XP right now. I originally tried this on a 64 bit Win 7 -- with either archecture, I get the same error though. At least I'm consistent.

my preldelta matches. It should. I didn't modify it.

=encoding utf8

=head1 NAME

perldelta - what is new for perl v5.16.3

=head1 DESCRIPTION
[download]

I did try to see what is in $contents and nothing was there. If I modify pod_lib.pl like so:

open Fpod, $filename or die "Can't read $filename: $!";
local $/;
my $filepod = <Fpod>;
close Fpod;

my $contents = $filepod;
[download]

then that gets me past the original problem of "Can't extract version from pod/perldelta.pod"... that is fixed from the code snip just above.

However, with using that code snippet, it now throws another error later down in pod_lib.pl. At this point, I have an uneasy feeling about chasing modifications to pod_lib code when it has worked for others out of the box.

Thanks!

In reply to Re^6: Compile PERL from source on Windows by MGoBlue
in thread Compile PERL from source on Windows by MGoBlue

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


XP is just a number
	PerlMonks