Xref: utzoo gnu.gcc:22 gnu.g++:12 comp.sys.apollo:1470
Path: utzoo!yunexus!geac!syntron!jtsv16!uunet!tut.cis.ohio-state.edu!mailrus!rutgers!ucla-cs!admin.cognet.ucla.edu!casey
From: casey@admin.cognet.ucla.edu (Casey Leedom)
Newsgroups: gnu.gcc,gnu.g++,comp.sys.apollo
Subject: Re: Need GNU C and C++ for Apollo
Message-ID: <16710@shemp.CS.UCLA.EDU>
Date: 11 Oct 88 22:35:50 GMT
Article-I.D.: shemp.16710
References: <16394@shemp.CS.UCLA.EDU> <1988Oct7.103554.27747@mntgfx.mentor.com>
Sender: news@CS.UCLA.EDU
Reply-To: casey@cs.ucla.edu.UUCP (Casey Leedom)
Organization: UCLA
Lines: 21

Dave Clemans (dclemans.falcon@mntgfx.mentor.com) writes:
> The simplest way would be to purchase the C++ product from Apollo (or
> from Glockenspiel; I think Apollo is currently just reselling
> Glockenspiel's port?).  This would be a port of AT&T's code (version 1.2).
> 
> The big problem with getting GNU CC/G++ on Apollo's & SR10 is that Apollo
> uses (a slightly extended) COFF format object file, and GNU generates
> A.OUT format files.

  Yes, I've now heard about the BETA availability of an AT&T based C++
from Apollo and I've also heard about the problems porting GNU C++ to the
Apollo (from Michael Tiemann as a matter of fact).  The problem with the
C++ that Apollo is working with is that it's based on AT&T preprocessor.
That means it's going to be slow, incomplete, and expensive.  That isn't
a combination I relish.  I would much rather deal with a product that's
near the front line of C++ language development.

  Thanks for your note.  So far I have little to report officially.
We'll just have to see how a couple of my feelers pan out.

Casey