[comp.sys.amiga] Request for C Compiler info

smithey@esosun.UUCP (Brian Smithey) (09/29/88)

Hi again,

Sorry if this has been gone over a million times before, I'm new
around here.

I'm getting ready to buy a C compiler for my Amiga.  Can anyone
fill me in on what you get and don't get in the following packages:

- Lattice C
- Lattice C Professional
- Manx Aztec C68k/Am-p Professional System
- Manx Aztec C68k/Am-d Developer System

I asked around at a couple of the local Amiga shops, neither of them
had any of these in stock nor could they tell me anything about the
products, other than the fact that they would be happy to order
any of them for me.

I'm not interested in hearing about Manx vs. Lattice as much as
I am interested in the differences between the less expensive
(Lattice C, Aztec Professional) and more expensive (Lattice
Professional, Aztec Developer).  However, I am interested in
availability of a source level debugger, which I have seen
advertised for Aztec but not for Lattice.  Set me straight on
this if I'm wrong.

E-mail the info, I'll summarize or send personal replies to those
also interested in this.


Thanks,

Brian


P.S.  Thanks to all who replied to my previous request for Common
Lisp info.  I picked up Xlisp 1.7 on Fish #39; while not Common,
it will do for the class I'm taking.



-- 
Brian Smithey                     |
Geophysics Division               |  {ucbvax!ucsd,uunet!seismo}!esosun!smithey
Science Applications Int'l Corp.  |  esosun!smithey@seismo.css.gov
San Diego, CA                     |

Sullivan@cup.portal.com (10/01/88)

>- Manx Aztec C68k/Am-p Professional System
>- Manx Aztec C68k/Am-d Developer System
>
>I'm not interested in hearing about Manx vs. Lattice as much as
>I am interested in the differences between the less expensive
>(Lattice C, Aztec Professional) and more expensive (Lattice
>Professional, Aztec Developer).  However, I am interested in
>availability of a source level debugger, which I have seen
>advertised for Aztec but not for Lattice.  Set me straight on
>this if I'm wrong.
>
The only differences between Lattice Professional and Lattice
Developer (that I'm aware of) is that the developer package has
a couple of added utilities, and costs about $80 more.  The 
manual distributed with each package is the same.
 
The utilities:
 
MAKE	using a .make file, MAKE will automatically search for
        each object code versions of each of the source files,
	compare the last access dates, and compile and link
	any files which have been updated.

GREP	searches files for character strings using some limited
	but reasonably useful string pattern matching.  (The 
	limitation is in speed, not in power here.)

DIFF	compares two files and prints out any differences. The
	version of DIFF included in the MANX package is both
	slow, and very easy to get completely out of synch. It
	works well if you don't ever delete anything from your
	source files.

OBD	lists the loader items in an object file. 

ORD	sorts an object file to minimize the number of backward
	references.  This is the only really handy utility that
	you wouldn't be able to write for yourself in a couple
	of hours.  Naturally it doesn't have any impact if you
	don't use excessively large linkable object files.
 
Z	is a VI like editor.  It is fairly complete, but is very
	slow, and not at all amiga-ized.  Of the lot, this is
	probably the most disappointing.  (Try searching for a
	simple character string in a 32k file.)  Not only is
	this editor slow, however; but it is also incapable of
	editing files which are larger than your available 
	memory.  (All of the disadvantages, and none of the
	advantages.)
 
I would strongly recommend saving your money on the developer 
package and getting the source code debugger instead.  (I didn't.)
Editors (even VI compatible ones) are common in the public domain.
Personally, I use the micro Emacs package that comes on your extras
disk.  The source code debugger works very well for a version 1 
product, and will no doubt be enhanced to avoid some of the guru
traps that it can fall into.  It is especially handy to be able to
test small subroutines in the debugger without having to write the
code to do so.  Just eval the function, and it will return your 
results but calling the function you named with the values you 
specified.

                           -Sullivan Segall
                            (still looking for a 68881 that
                             can be piggy-backed on a 68000)
_____________________________________________________________

/V\  My opinions are guaranteed to be worth at least what you
 '   paid for them.   If you are dissatisfied,  please return
     them to the nearest vendor for a full and prompt refund.
To Quote the immortal Socrates: "I drank what?" -Sullivan
_____________________________________________________________

Mail to: ...sun!portal!cup.portal.com!Sullivan or
         Sullivan@cup.portal.com