[pgrabo]

Hi.

My problem is very simple. I don't have MacOS X so I ask you :
on macos X is return character :
-> chr(13)+chr(10) (Like Windows or UNIX)
-> chr(13) (like MacOS Classic) ?

Thank you very much,
Pierre.

[lindberg]

The Cocoa and BSD APIs use the UNIX convention, a bare linefeed only -- chr(10). I think this is the most typical case you'll find on the system, at least at the lower levels.

I'm pretty sure the Carbon APIs and Classic apps will still use the classic MacOS one, chr(13) (carriage return).

I'm not sure about things like CoreFoundation which is used by both Cocoa and Carbon, but I'm guessing it uses the UNIX-style ones too (the XML preferences files, for example).

Nothing uses the Windows convention, chr(13)+chr(10).

[honeydew]

FYI. In Java, you can inspect the line.separator environment variable to determine the return character(s) of the host operating system. Use this to avoid hard-coding a certain convention into your application.

<font face = "courier">String sep = System.getProperty( "line.separator" );</font>


Edit: fixed a typo.

[ 06-18-2001: Message edited by: honeydew ]

[clarkgoble]

In this day of networks and files of relatively unknown origin (PC, Mac, *nix) shouldn't we write software that doesn't make assumptions about what line break characters are used?

I mean just glancing on my directory I have multiple text files that are in all three formats. I'm just glad that my primary coding app (Vusual Studio - no jeers please) is able to deal with them all. Whenever I write my own I always assume any type might be present. (Although to be fair I use Lex a lot for translating text documents, so it is easy for me)