Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!rutgers!netnews.upenn.edu!msuinfo!frith!dailey From: dailey@frith.uucp (Chris Dailey) Newsgroups: comp.sys.amiga.tech Subject: Re: Lattice C++ Keywords: C++, C, compiler, Lattice Message-ID: <1990Dec17.141922.27747@msuinfo.cl.msu.edu> Date: 17 Dec 90 14:19:22 GMT References: <1990Dec12.175455.13985@agate.berkeley.edu> <1990Dec15.192957.13441@batcomputer.tn.cornell.edu> Sender: news@msuinfo.cl.msu.edu Organization: Michigan State University Lines: 25 In article <1990Dec15.192957.13441@batcomputer.tn.cornell.edu> riley@batcomputer.tn.cornell.edu (Daniel S. Riley) writes: >SAS has said, on BIX, that they are working on an SAS C++ compiler. >This will be a C++ to 68000 code compiler, not a C++ to C translator >like the current Lattice product. No word yet on release date, or >upgrade policies. I don't need a C++ compiler *right* *now*, so I'm >going to wait. I've heard it may be ready by Fall '90, but there are many factors that could easily make that sooner or later. I should be getting a 3000 (or maybe a 3500 or 4000 by then??? :) around then and this is one of my planned purchases. >disclaimer: I just read about it, so that's all I know. My disclaimer: everything I said above is subject to change. Especially the bit about me getting a 3000 if my fiance-then-wife changes her mind. ;) >-Dan Riley (riley@theory.tn.cornell.edu, cornell!batcomputer!riley) >-Wilson Lab, Cornell University -- Chris Dailey dailey@(frith.egr|cpsin.cps).msu.edu BRD += DDR; DDR = NULL; num_countries --;