On Tue, Aug 4, 2015 at 12:33 AM, Mike Flannigan <mikef...@att.net> wrote:
> Thanks for confirming that. Chomp certainly doesn't fix
> the problem.
>
chomp won't help, in my example it will only get you from
$VAR1 = [
"foo\r\n",
"bar\r\n",
"quux\r\n"
];
to
$VAR1 = [
"foo\r",
"bar\r",
"quux\r"
];
By default, chomp doesn't strip CR LF, as $/ is "\n" even on Windows.
Reading a file on Windows in non-binmode will convert CR LF to "\n".
It's a bit frustrating, but I have my fix.
>
I'm surprised I was the one to point this out.
>
Must be very few of us Windows par users.
My guess would be that the majority of PAR users is on Windows, but using
__DATA__ is rare.
Or at least using the data in a way that is susceptible to CRLF v LF
corruption.
Cheers, Roderich
