Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!ames!ucbcad!ucbvax!CORY.BERKELEY.EDU!dillon
From: dillon@CORY.BERKELEY.EDU.UUCP
Newsgroups: comp.sys.amiga
Subject: Re: Portable "C" Code
Message-ID: <8704020726.AA05684@cory.Berkeley.EDU>
Date: Thu, 2-Apr-87 02:26:45 EST
Article-I.D.: cory.8704020726.AA05684
Posted: Thu Apr  2 02:26:45 1987
Date-Received: Sat, 4-Apr-87 10:47:50 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 22


	I now have both Lattice and Aztec C, and I've found that it's virtually
impossible to write code compatible with both and still be able to write 
efficiently.  Personally, I now use Aztec almost exclusively (Thanks Jim!),
and even though I always use the +L option for 32 bit ints, my code would
still require quite a bit of hacking of the header files before one could
get it to work with Lattice.  In fact, even Aztec users would have to do
some hacking to be able to compile it since I use a very automated 
enviroment (have cc and ln aliased, etc...).

	This is one of the reasons why I've stopped posting source for 
programs such as DME.... I have no desire to spend 12 hours making it work
on other peoples compiler enviroments, or even to standardize it to a
generic enviroment.  I rely heavily on my shell and the existance of
certain control files (my 'standard' enviroment) when working on a program.

	BTW, the source is *still* available on request if anybody's 
interested.  Also, I've noticed that 32 bit ints don't really increase
code size all that much.  What really makes the difference is the small
code and data model (using relative address for globals).

					-Matt