Well, I wasn’t specific enough. I know chr(10) is the Unix end of line character and is therefore of some use. What I don’t get is does chr(10) alone makes sense under Windows?
In other words, their choice of chr(13)+chr(10) has always looked silly to me.
As with everything else on Windows, it exists for legacy reasons.
I don’t know if you remember when macOS went from 9 to 10, but the line ending changed at that same time from chr(13) to chr(10). There was absolute madness when it came to apps that read text and assumed line endings would be one way or the other.
When is Windows going to break with this madness?
Oh I remember very well! Some components would still use Chr(13) while others where updated to Chr(10). IIRC, RB/RS used Chr(10) in Carbon but switched in Chr(13) for Cocoa.
Never, I should hope. The other two platforms have it wrong.
1 Like