Xref: utzoo comp.lang.fortran:4819 comp.unix.cray:259
Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!think.com!sdd.hp.com!usc!ucsd!scripps!mikec
From: mikec@scripps.edu (Mike A Christensen)
Newsgroups: comp.lang.fortran,comp.unix.cray
Subject: Re: CPP "problems" (was Re: why has Cray dropped CPP support from cf77?)
Message-ID: <1108@riscsm.scripps.edu>
Date: 20 Feb 91 19:29:54 GMT
References: <1298@red8.qtp.ufl.edu> <1991Feb18.145116.3840@convex.com> <1300@red8.qtp.ufl.edu> <1991Feb19.003449.1768@ariel.unm.edu>
Sender: news@Scripps.EDU
Followup-To: comp.lang.fortran
Organization: Research Institute of Scripps Clinic; La Jolla, CA
Lines: 9

I think we have a misunderstanding here, from my communication with Cray
software development, they are REPLACING the functionality of CPP with a
mostly equivalent (i.e. should take most C preprocessor directives) fortran
preprocessor.  This preprocessor will know about Fortran comments (especially
ones that begin with CRAY in CC1...) and various other problems with using
the C preprocessor on Fortran code.  I did the same panic when I saw the
comment from CF77 about ".F" files going away and not automatically running
the C preprocessor, and it took me several phone calls to finally get what
the "real" answer was.