This is very informative kcott, thanks :)
However, it doesn't help me understand why on Windows, when printing to a file-based file handle, an \n is printed by default as \r\n into the file (without any binmode or IO trickery, it just does so naturally.
However, the default record separator \r\n is not printed to a memory file based handle, it is printed only as \n. I would expect that regardless of type of handle, the default OS record separator would be used. I can't find anywhere that states this discrepancy between a real file and printing the exact same thing to a scalar reference acting as a file handle.
That, or I'm missing something very basic.
In reply to Re^2: Is there a way to open a memory file with binmode :raw?
by stevieb
in thread Is there a way to open a memory file with binmode :raw?
by stevieb
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |