Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!cernvax!chx400!chx400!bernina!igc.ethz.ch!torda
From: torda@igc.ethz.ch (Andrew Torda )
Newsgroups: comp.lang.c++
Subject: Re: How is Sun C++ ??
Keywords: Sun C++ 2.0
Message-ID: <1991Mar4.084029@igc.ethz.ch>
Date: 4 Mar 91 07:40:29 GMT
References: <1991Feb18.154509.13664@dit.upm.es> <1803@tcs.tcs.com> <4190@lupine.NCD.COM>
Sender: news@bernina.ethz.ch (USENET News System)
Reply-To: torda@igc.ethz.ch (Andrew Torda )
Organization: InformatikgestutzteChemie, ETH, Zurich
Lines: 25
Nntp-Posting-Host: hermitage

In article <4190@lupine.NCD.COM>, rfg@NCD.COM (Ron Guilmette) writes:

> Another minor annoyance for users of Sun C++ is that the `CC' command is
> implemented as a compiled program (supplied as binary only) rather than
> as the shell script (in source form) which usually comes with cfront ports.

No. This is just not true. There is a script. It starts like ...
-------------------
#!/bin/sh
PATH=/usr/lang:/bin:/usr/bin
# @(#)CC-driver 1.19 (Sun) 89/07/21
--------------------
and so on...


> This means that if you want to get in and hack your own local tricks into
> the CC script... well, you can't with Sun C++.

Yes you can.
I have swapped C compilers, played with options, paths etc...

I am ready to be corrected if there is a newer/different version, but check
the ID at the top of the script I included.
--
Andrew Torda, ETH, Zurich