🚀 go-pugleaf

In article <24892.26985ff4@kuhub.cc.ukans.edu> markv@kuhub.cc.ukans.edu writes:

>>>Is the Lattice C++ compiler based on C++ ver. 1, or C++ ver.2?  

>> As I recall, the Lattice V1.00 cfront was based on AT&T cfront 1.1a.

>Lattice C++ is based on CFront 1.2 (not 1.1).  As of six months ago
>Lattice had plans for both a native code and a 2.0 level product.

Well, every time I run it, it claims to be based on V1.1a.  Unless the 
cfront program is lying to me, that would be pretty conclusive, eh?

>But, the Lattice C++ package includes a full implementation of the
>Lattice 4.0 level compiler (with support for 100 char identifiers
>added) so you HAVE a working *mostly* ANSI C Compiler.

What they left out was documentation on the V4.x compiler, because they
obviously don't intend to support the use of the C compiler as part of the
C++ distribution.  Like, when/if the single phase compiler is written, the
LC1 program, at least, disappears from the Lattice distribution.

>That scale is about right.  You had better have a LOT of memory (like
>over a meg FREE) if you want to use C++ or Lattice's global optimizer.
>Making the compiler resident (with Lattice remember you need to
>Resident LC1 and LC2 besides LC) you get a HUGE time gain when doing
>large multi-file makes.  Putting QUAD: in RAM: helps, and doens't eat
>much memory since you only have one .q file at a time.

Absolutely.  The cfront program also needs a very large stack, I usually
give it 1/2 a meg or so.  It'll run with a much smaller one, but it tends
to crash much more.

>Mark Gooderum			Only...		\    Good Cheer !!!
-- 
Dave Haynie Commodore-Amiga (Amiga 3000) "The Crew That Never Rests"
   {uunet|pyramid|rutgers}!cbmvax!daveh      PLINK: hazy     BIX: hazy
	"I have been given the freedom to do as I see fit" -REM