Xref: utzoo comp.lang.fortran:4798 comp.unix.cray:252 Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!clyde.concordia.ca!nstn.ns.ca!news.cs.indiana.edu!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!usc!apple!sun-barr!newstop!exodus!exodus-bb!khb From: khb@chiba.Eng.Sun.COM (Keith Bierman fpgroup) Newsgroups: comp.lang.fortran,comp.unix.cray Subject: Re: why has Cray dropped CPP support from cf77? Message-ID: Date: 19 Feb 91 21:32:13 GMT References: <1298@red8.qtp.ufl.edu> <1991Feb19.162007.28774@ncsa.uiuc.edu> Sender: news@exodus.Eng.Sun.COM Followup-To: comp.lang.fortran Organization: Sun MegaSystems Lines: 30 In-reply-to: hirchert@ncsa.uiuc.edu's message of 19 Feb 91 16:20:07 GMT In article <1991Feb19.162007.28774@ncsa.uiuc.edu> hirchert@ncsa.uiuc.edu (Kurt Hirchert) writes: >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, .... Inasmuch as unix f77 has traditionally handled .F files in a particular fashion (admittedly there are sometime a few implementation specific details ;>) when wearing _my_ consumer hat, I'd very much complain if a vendor made it stop working. There are several ways for the vendor to ensure that f77 continue working; as a consumer I don't care how. Of course, as a vendor I have ideas ..... ;> But seriously, if you folks like the functionality of #ifdef and friends, you will have to complain whenever someone leaves it out (from this discussion Cray, from others, IBM with their xlf on the RS/6000 come to mind as the only exceptions in UnixLand). -- ---------------------------------------------------------------- Keith H. Bierman kbierman@Eng.Sun.COM | khb@chiba.Eng.Sun.COM SMI 2550 Garcia 12-33 | (415 336 2648) Mountain View, CA 94043