NetNews Usenet Archive 1993 #1/NN_1993_1.iso/spool/comp/sys/atari/st/tech/6523

Internet Message Format | 1993-01-07 | 1.6 KB

Path: sparky!uunet!mcsun!uknet!fulcrum!its!silver.its.bt.co.uk!jvt
From: [e-mail] (John Trickey)
Newsgroups: comp.sys.atari.st.tech
Subject: Re: Porting UNIX Code to the ST
Message-ID: <[e-mail]>
Date: 7 Jan 93 12:43:24 GMT
References: <[e-mail]>
Sender: @its.bt.co.uk
Organization: BT Group Computing Services, Birmingham, UK
Lines: 27

In article <[e-mail]> [e-mail] writes:
>
>I have some code that generates a binary file - I compiled it with GCC 2.3.1
>and ran it on the ST - it works fine, it generates a binary file; however, the
>print statements seem to be outputting a CNTRL-M (^M) - I don't need these
>extra characters what should I do to get rid of them???


The problem you have encountered is that Unix treats all files alike while
DOS, TOS etc do not. In Unix the open is fopen(filename,mode) where mode is
a char * of "a","r","w","r+","w+","a+". In TOS these are for text files with
CRLF being converted to LF on input and LF being converted to CRLF on output.
Note CR is ^M.
To switch this off you need to open the file in binary mode. These modes
are "ab","rb","wb","rb+","wb+","ab+". The format "r+b" etc is also acceptable.

NOTE for developers:
There is nothing stopping you using these binary formats in Unix. Any decent
implementation will recognize them. They obviously will have no effect but
its then easy to port to DOS-type environments.

John
--
John Trickey <[e-mail]>
       Voice: [phone]     Fax: [phone]
(Home) <[e-mail]> || <[e-mail]> || G4REV @ GB7FLG
       [phone]