Xref: utzoo comp.lang.fortran:4824 comp.unix.cray:262
Path: utzoo!mnetor!tmsoft!torsqnt!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!wuarchive!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!mp.cs.niu.edu!ux1.cso.uiuc.edu!hirchert
From: hirchert@ncsa.uiuc.edu (Kurt Hirchert)
Newsgroups: comp.lang.fortran,comp.unix.cray
Subject: Re: why has Cray dropped CPP support from cf77?
Message-ID: <1991Feb19.162007.28774@ncsa.uiuc.edu>
Date: 19 Feb 91 16:20:07 GMT
References: <1298@red8.qtp.ufl.edu>
Sender: news@ux1.cso.uiuc.edu (News)
Organization: NCSA - National Center for Supercomputing Applications
Lines: 23
Originator: hirchert@harriett

In article <1298@red8.qtp.ufl.edu> bernhold@qtp.ufl.edu (David E. Bernholdt) writes:
>
>The latest release of cf77 no longer supports automaticly running .F
>files through CPP before compiling them.  This move seems to be a step
>backward from the what I think is a _very_ useful feature common to
>_many_ unix-based fortran implementations.  Does anyone know why they
>did it?

I don't know, but I could guess.  As I understand it, the standard C compiler
(scc) doesn't use cpp, but does preprocessing internally, instead.  Under
Unicos 6.0, scc becomes the default cc, and the previous cc becomes pcc,
presumably with the intention of eventually eliminating support for pcc.
If cpp is seen as being part of a product that is no longer going to be
supported, then I can see why they would not want to continue using it in
one of their other supported products.

Now, scc has switches so that it can be used as a replacement for cpp, so
I suppose you could lobby with CRI to run .F files through that, but I can
imagine the confusion when the documentation for cf77 says that under some
circumstances it runs your Fortran source through cc!
-- 
Kurt W. Hirchert     hirchert@ncsa.uiuc.edu
National Center for Supercomputing Applications