Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site osu-eddie.UUCP
Path: utzoo!watmath!clyde!cbosgd!osu-eddie!pritch
From: pritch@osu-eddie.UUCP (Norman Pritchett)
Newsgroups: net.lang.c,net.lang.f77
Subject: Re: VAX VMS C / UNIX C Compatibility -- Need Info
Message-ID: <545@osu-eddie.UUCP>
Date: Tue, 20-Aug-85 21:36:19 EDT
Article-I.D.: osu-eddi.545
Posted: Tue Aug 20 21:36:19 1985
Date-Received: Sat, 24-Aug-85 03:41:31 EDT
References: <488@rdin.UUCP> <249@watmum.UUCP>
Organization: Ohio State Univ., CIS Dept., Cols, Oh.
Lines: 19
Xref: watmath net.lang.c:6120 net.lang.f77:370

cdshaw writes:
> VMS is very record-ish, while stream i/o is the unix thing. Unfortunately,
> port didn't work because we didn't really spend the effort required to do
> the QIO's required to fake stream i/o on VMS. 


Huh?  On input Vax-11 C converts records with any attribute (implied
carriage control, print carriage control, FORTRAN carriage control, null,
and VFC) to stream format (read your "Programming in VAX-11 C" book
AA-L370A-TE) so everything always looks like stream files on input.  On
output, Vax-11 C creates stream files unless you go through the immense
amount of effort to specify otherwise.
-- 
-----------------------------------
Norm Pritchett
UUCP:   cbosgd!osu-eddie!pritch		P.O. Box 3393
CSNET:  pritch@ohio-state		Columbus OH 43210
BITNET: TS1703 at OHSTVMA
Bellnet: (614) 422-0885