Re^4: Native newline encoding

[sauoq]

That's a bit obvious :)

Erm... what's the obvious part? That I don't do Windows or that it should be 0d0a? Or both?

He asked for the "native newline encoding of the OS"... It doesn't matter what writes it. Maybe it's because I don't do Windows but do have to deal the bastardized text files that come from Windows that the distinction is meaningless. I know I don't care whether it is Perl or the run time writing the characters. That they are there is what matters.

[BrowserUk]

He asked for the "native newline encoding of the OS"... It doesn't matter what writes it.

Sorry mate! But it absolutely does matter.

Which is why my post contains two questions which salva will get around to answering (or not) in his own time.

[sauoq]

But it absolutely does matter.

No, it doesn't. To be clear (because we could confuse others with what we are saying matters and doesn't if we continue along this line):

I am saying it doesn't matter what writes the characters, only that they are there.

While you are saying it doesn't matter that they are there because of what writes them.

And, you know, this is what I hate about Windows... the pervasive attitude that the OS is doing something for you that you can just ignore.

Here's an assignment that would illustrate the difference... You are to write a textual file with X lines. Each line will have Y number of characters not including the newline. X and Y will be determined at runtime. Before writing the file, tell the user how big it will be on disk.

Update: Make it portable, of course.

[BrowserUk]

I am saying it doesn't matter what writes the characters, only that they are there.

Sorry, but you cannot possibly know that unless you have read salva's mind and thereby know what his purpose is!

All the rest is supposition.