Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!bloom-beacon!oberon!cit-vax!ucla-cs!zen!ucbvax!CORY.BERKELEY.EDU!dillon
From: dillon@CORY.BERKELEY.EDU (Matt Dillon)
Newsgroups: comp.sys.amiga
Subject: Re: Request for Compiler Info
Message-ID: <8710200436.AA19519@cory.Berkeley.EDU>
Date: Tue, 20-Oct-87 00:36:41 EDT
Article-I.D.: cory.8710200436.AA19519
Posted: Tue Oct 20 00:36:41 1987
Date-Received: Wed, 21-Oct-87 06:16:26 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 49

>In article <4443@zen.berkeley.edu> (Jonathan Dubman) writes:
>Having gained little from the objective reviews ("Both are good systems...")
>I am interested in religious statements from any owners of MANX and Lattice,
>especially from those who have seen Lattice 4.0 in action.  Unless the flame
>is low, please mail such statements PRIVATELY. 

>[Minimal flamage here, just the facts ]
>
>I own Lattice, (thats what I started with), have nothing but hearsay to report
>on 4.0 although they should get my Update card today so I expect my copy RSN.

	Here's some additions to Chuck's response to Jonathan's original
message from one who owns Aztec.

>	-What are the classes of source code incompatibility?

>	-Size of code? Speed of compilation? 

	I don't think it is an issue anymore.  Lattice 4.0 is supposed to
be as good (or better) as the current Aztec release, and the next aztec
releaes is supposed to better, etc..... but they don't, or wont differ all
that much as time moves along.... there is a theoretical limit.

>	 Provisions for LARGE programs?

	*No* 68000 C compiler that I know of has problems with code/data size.
Only IBM-PC compilers have such problems.

>>  	Scatter-loading?  Overlays?
>As far as I know only Lattice does these, and on Overlays only in 4.0.

	Aztec supports scatter loading and overlays as of 3.4a

>>	 Assembler included?  68010/68020/68881 provisions in compiler and
>>	 assembler?
>Yes on both counts. In 4.0 Lattice claims to have a totally compatible 
>Assembler (can use the C/A .i files). 

	Aztec also... in fact, the C compiler produces assembly so an
Aztec compilation second stage *is* the assembler.  I don't know if Lattice
has moved from their QUAD intermediate file format to an assembler as far 
as compilation goes.

	One thing I have gotten used to with Aztec C is the use of 'void *'..
meaning a pointer to anything.  Does Lattice implement this?  As far as
the ever evolving C spec, both Lattice And Manx are moving along parallel
paths.

				-Matt