Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site gumby.UUCP
Path: utzoo!watmath!clyde!cbosgd!cbdkc1!desoto!packard!edsel!bentley!hoxna!houxm!mhuxr!ulysses!allegra!bellcore!decvax!genrad!teddy!panda!talcott!harvard!seismo!uwvax!gumby!g-frank
From: g-frank@gumby.UUCP
Newsgroups: net.lang.c
Subject: Re: Lattice/UNIX incompatibility
Message-ID: <233@gumby.UUCP>
Date: Tue, 25-Dec-84 16:20:05 EST
Article-I.D.: gumby.233
Posted: Tue Dec 25 16:20:05 1984
Date-Received: Thu, 27-Dec-84 03:28:49 EST
References: <344@rna.UUCP>
Organization: U of Wisconsin CS Dept
Lines: 16

> I looked at a Lattice C manual a few days
> ago.  The list of differences between Lattice C and K+R C seemed large,
> and then in browsing through the reference section I discovered further
> incompatibilities between Lattice and K+R.  I don't have similar
> reservations about Mark Williams compiler.
> 
> Kaare Christian

Which version of Lattice C did you look at?  As of 2.14, the "UNIX" interface
is much improved, with many more functions, and bit more sense to the ones
there are.  Lattice does have its own naming conventions for stuff, but also
offers the UNIX names, as far as I can tell.  The only big problem is the need
to use a "b" in the opentype string when opening files for "binary" (that is,
no translation of CR/LF pairs, no recognition of ^Z as EOF, etc.).  This is
100% UNIX incompatible, of course, but it's hard to see how else to resolve
it, given PC-DOS.