🚀 go-pugleaf

daveh@cbmvax.commodore.com (Dave Haynie) writes:


>>What are the relative speeds for the Aztec C, Lattice C, and Lattice C++?  

>Like I said, I don't have the new compiler, but the time based on the ones
>I've used go on this timeline:


>  -+------------+--------+---------+-----------+----------------+---------+-
>   |            |	 |         |           |                |         |
>A Sneeze      Manx    Lattice   A Trip to    Lattice         Lattice   Out for
>	      3.6a      5.0     the Coffee    3.03           C++ 1.0   a cold
>                                 Machine                                Beer

Are these compile times or speeds of the executable program?
More explanation is necessary for this to be meaningful.

As for one of the original posted questions about buying or going with
a PD compiler, a PD product is not equivalent to a purchased product
for several reasons (even if the code generation was equivalent, which
from what I observe, it isn't).  One must also consider

	1) Who will fix the bugs first? Someone who is paid to
	do it for eight or more hours/day or someone who does
        it in their spare time.

	2) What is the technical support plan for the PD product?
	What happens when the author is on vacation or gets tired 
	of answering questions?  What's the documentation like?
	
	3) What is the upgrade/improvement plan on a free product? 
	Does it come with an assembler, a symbolic debugger,
	68020 or 68881 support?

 I guess it depends how much time you have available to mess around
 with the added problems of PD. If I was building a commercial product,
 or even a serious amateur, though.  I don't think I would mess around
 with PD compiler tools for the same reasons I choose to buy the
 hardware instead of make it myself.

Russ Sorber
Software Contractor Currently at Motorola Cellular Div.