Hi,
Thanks for responding to my email.
It looks like I had a typo in my explanation of the slurping problem. Thanks
for catching that.
Actually, I had the correct input field separator in my code, and simply
miswrote it in my explanation.
The perldoc is always a good place to start.
I was using
On Oct 28, Renee Halbrook said:
My perl interpreter display does not recognize \r for a newline character
for standard out, so it simply printed the same line over on top of the
previous line, making it look like it was only reading one line total.
The slurping was working fine, but the display
On Oct 28, 2005, at 15:09, Jeff 'japhy' Pinyan wrote:
On Oct 28, Renee Halbrook said:
My perl interpreter display does not recognize \r for a newline
character
for standard out, so it simply printed the same line over on top
of the
previous line, making it look like it was only reading
In Mac OS X the newline is \012 and that is what \n is eq to. I was
told in MacPerl (for MacOS pre X) the underlying codes of \n and \r
were switched (wrt to the rest of platforms), but still \n is the
logical newline everywhere.
--The specs the file was created from:
Filemaker version
On Oct 28, 2005, at 15:29, Renee Halbrook wrote:
In Mac OS X the newline is \012 and that is what \n is eq to. I was
told in MacPerl (for MacOS pre X) the underlying codes of \n and \r
were switched (wrt to the rest of platforms), but still \n is the
logical newline everywhere.
--The specs
