in reply to Re^7: Native newline encoding
in thread Native newline encoding

This: Hence, I knew that he wasn't asking "What are the line endings"? by the way, is neither. That's just something that you apparently pulled out of thin air.

No. You raised that when you tried to suggest that I was trying to hide something.

then I thought maybe you were giving a ... example to make a ... point

OoooooW And you were so close ... but then no. The stupidity kicked in again.

The point of the example -- that was clearly followed with the question: "Maybe not so useful depending upon your purpose?" -- was to point out that the value of "\n" is not OS dependent; but rather encoding dependent!.

That what characters will end up on disk when you write a newline to a file, cannot be determined from discovering what OS you are running under alone

.

A point that I'm pretty sure that salva will have got from my original post, but one that you so completely missed, and are still trying arm-wave, distract and dissemble your way past.

I'm done now, waffle on all you like.


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.

The start of some sanity?

Replies are listed 'Best First'.
A reply falls below the community's threshold of quality. You may see it by logging in.