Article View: comp.sys.amiga.tech
Article #7413Re: Lattice C++
From: Pete Goodeve
Date: Wed, 12 Dec 1990 17:54
Date: Wed, 12 Dec 1990 17:54
37 lines
2619 bytes
2619 bytes
In <kisworo.660924569@cutmcvax.cs.curtin.edu.au> (11 Dec),
Marsudi Kisworo (kisworo@cutmcvax.cs.curtin.edu.au) writes:
> [....] before I buy the LC++, I want to know whether
> it compiles ordinary LC source since I have written a lot
> of routines in C. Is there anybody in the netland who
> know this and have experience with this ? Also is there
> any problem arises when porting Lattice C code to
> Lattice C++ code ? Will LC++ generates C code like Unix C++ ?
I've had Lattice C++ for about three years, and it has mostly worked
fine for me. (I actually used it to cross-develop a (large) project that
was finally compiled under Zortech on that machine we don't mention.
Virtually all of the few minor problems I had were due to (early) Zortech's
deficiencies, except for one place -- don't remember the circumstances
I'm afraid -- where the Lattice Cfront section generated bad C code!)
Lattice C++ IS basically a precompiler (Cfront) for their standard C
compiler. It came with version 4 of that; I'm using 5.04 with no problems.
(I have 5.1 but haven't checked it with that yet.) I don't see any
problem with importing standard C routines, except for the few intolerances
that C++ has (noted in Stroustrup I think); I'm not sure whether C++
accepts old style parameter declarations or not -- I think it does, with
a warning. I always use the new convention these days. I have on a few
occasions simply dropped in some plain C from somewhere else, without
troubles.
Cfront does of course generate plain C source, but this calls functions
from the C++ library (in addition to lc.lib) to do most of the special
tricks, so you can't easily drop thus source back into a plain C program.
It's perfectly all right to link in plain C object modules with C++, though.
My real worry about purchasing it at this stage would be its current
status. Lattice never really did any updating, and now that SAS has
taken over C development, I have no idea what their plans are. What
about it, SAS?
-- Pete --
Technical Details
Message-ID:
<1990Dec12.175455.13985@agate.berkeley.edu>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!think.com!linus!agate!violet.berkeley.edu!peteReferences:
<kisworo.660924569@cutmcvax.cs.curtin.edu.au>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!think.com!linus!agate!violet.berkeley.edu!pete From: pete@violet.berkeley.edu (Pete Goodeve) Newsgroups: comp.sys.amiga.tech Subject: Re: Lattice C++ Keywords: C++, C, compiler, Lattice Message-ID: <1990Dec12.175455.13985@agate.berkeley.edu> Date: 12 Dec 90 17:54:55 GMT References: <kisworo.660924569@cutmcvax.cs.curtin.edu.au> Sender: usenet@agate.berkeley.edu (USENET Administrator) Organization: University of California, Berkeley Lines: 37