I've opened and am using read FH, $nextchr, 1 to read one character at a time from a data file.
I've looked at the data file from within a hex editor and the lines are definately termined with 0x0D followed by 0x0A - but when the read gets to the relevant place it only reads one 0x0A and there is no 0x0D to be seen.
Is there some kind of weirdness to do with how the machinery underneath read goes about dealing with carriage returns and new lines on different platforms?
-Andrew Tomazos <andrew@tomazos.com>
In reply to read and EOL weirdness on win32 by tomazos
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |