When is this really an issue? It's only when you are doing things over a network between platforms, never when you are using "native" software tools.
Is there already a defined convention for doing this? I know these platforms work together all the time over the internet, but I have never taken the time to understand what the low level issues are.
Web pages can be constructed and loaded on all platforms, how are web browsers designed to cope with these issues? I don't know the answer, but I suggest we find out, and do the same.
Don
Date: Mon, 20 Aug 2001 07:35:10 -0700
On Sunday, August 19, 2001, at 08:18 PM, Daniel Bump wrote:
David Denholm wrote:
My inclination would be to define that GTP uses LF for end of line, and treats CR as a whitespace character. Provided the protocol also defines that trailing whitespace will be ignored (which impacts things like sending filenames as parameters, since they could end in spaces). in space, for example) So then either CRLF or LF will work fine.
A disadvantage of this scheme is that printf("gtp response\n") would be broken on Macintosh, since CR is the Macintosh newline.
Mac C compilers output \r in place of \n.
PC C compliers output CRLF.
Easier to just execute when either a CR or LF is received, and allow the "null" command that lies between CRLF.
Pierce