Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!columbia!caip!princeton!allegra!ulysses!cbosgd!ucbvax!edison.GE.COM!jso
From: jso@edison.GE.COM (John Owens)
Newsgroups: mod.computers.vax
Subject: Problem with VAX C 2.x file writes
Message-ID: <8608272218.AA17362@edison.GE.COM>
Date: Wed, 27-Aug-86 18:18:12 EDT
Article-I.D.: edison.8608272218.AA17362
Posted: Wed Aug 27 18:18:12 1986
Date-Received: Thu, 28-Aug-86 22:46:07 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 26
Approved: info-vax@sri-kl.arpa

This message is being forwarded for a friend at a DECNet node.
Send all replies to me and I will forward them on to her.

John Owens		General Electric Company - Charlottesville, VA
jso@edison.GE.COM	old arpa: jso%edison.GE.COM@seismo.CSS.GOV
+1 804 978 5726		old uucp: {seismo,decuac,houxm,calma}!edison!jso

========================================================================
08/26/86 Libby Carpenter

- This problem was discovered on the microvax -

When creating text files that are used and input to VAX utilities, such as
the C compiler or macro assembler, we have been told by DEC S/W support to 
avoid "fprint" and "fwrite" and to use just "write" instead.

What is the story with this??

They are running VMS v4.4 and C v2.1 and have tried C v2.2 with same results.

Analyze/rms shows the file as corrupted.

With version 2.x of C the way they handle writes have been changed.

Temporary fix is to have the new line character as the last char. of the last 
write of the last line of the file.