|laziness, impatience, and hubris|
Re^3: Native newline encodingby BrowserUk (Pope)
|on May 22, 2012 at 18:10 UTC||Need Help??|
It should be, for example, 0d0a on Windows ... I don't really do Windows
That's a bit obvious :)
It isn't perl(*) that writes the extra character; it is the C runtime (when writing to a data file opened as text). Those extra characters are also stripped by the CRT when reading -- assuming text mode.
If Perl added them itself, then the CRT would also do it and you'd end up with a real mess.
perl; and Perl programmers shouldn't need to concern themselves with the details, because -- unless they are reading text files in bin mode; which they shouldn't be -- the addition and removal of the 'extra characters' should be entirely transparent.
(*) ignoring PerlIO which does; but only because it bypasses the CRT and then emulates it -- the point of which mystifies me, but there it is.
With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.