Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!sun-barr!lll-winken!sundance!jac From: jac@gandalf.llnl.gov (James A. Crotinger) Newsgroups: comp.unix.amiga Subject: Re: What commercial end-user applications are exist NOW for the A300 Message-ID: Date: 4 Apr 91 16:41:19 GMT References: <46522@ut-emx.uucp> Sender: usenet@lll-winken.LLNL.GOV Lines: 31 Nntp-Posting-Host: sundance.llnl.gov tbissett@nstar.rn.com (Travis Bissett) writes: > zebr360@ut-emx.uucp (Jerry Heyman) writes: > > Anyone want to speculate as to the requirement of the Lattice/SAS C compiler > > requirement? > > > My guess is that Comeau found it expedient to use a pre-existing set of > library and header files -- e.g. the Lattice libraries. > Sound like a reasonable hypothesis? Comeau's C++ product is a CFRONT port (so is Lattice's, but Comeau's is much newer [2.1 vs 1.2]). It translates C++ code to C. You still need a C compiler to do the final phase. I can only speculate as to why they require SAS C: Possibly because SAS C has already been tested as a backend to an earlier version of CFRONT. CFRONT can produce some gawd-awful C code and I've seen many C compilers choke when trying to compile it. Does anyone know if the arrival of Comeau C++ for AmigaDOS has derailed SAS's plan to market a new version of their C++ product? They had been planning to release a native C++ compiler (one which compiled directly to machine code) sometime in '91. Jim -- ----------------------------------------------------------------------------- James A. Crotinger Lawrence Livermore Natl Lab // The above views jac@moonshine.llnl.gov P.O. Box 808; L-630 \\ // are mine and are not (415) 422-0259 Livermore CA 94550 \\/ necessarily those of LLNL