Xref: utzoo comp.lang.fortran:4821 comp.unix.cray:261 comp.lang.perl:4183 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!asuvax!noao!ncar!elroy.jpl.nasa.gov!sdd.hp.com!spool.mu.edu!uunet!mcsun!ukc!stl!robobar!ronald From: ronald@robobar.co.uk (Ronald S H Khoo) Newsgroups: comp.lang.fortran,comp.unix.cray,comp.lang.perl Subject: Re: why has Cray dropped CPP support from cf77? Message-ID: <1991Feb21.075334.6299@robobar.co.uk> Date: 21 Feb 91 07:53:34 GMT References: <1991Feb19.230305.22563@convex.com> <1991Feb20.101450.18745@robobar.co.uk> <1991Feb20.190424.22590@convex.com> Followup-To: comp.lang.perl Organization: Robobar Ltd., Perivale, Middx., ENGLAND. Lines: 20 [ no longer a cray/fortran issue, I think, so followups redirected ] allison@convex.com (Brian Allison) writes: > I don't know about Cray, but Convex's cpp has a -pcc switch to force it to > (quoting the man page) "behave compatibly with earlier preprocessors that > were not ANSI C conforming." (Does Convex's .F.o default make rule call cpp -pcc ?) Hmm, so why did Tom say that he could no longer use cpp for his perl scripts ? Surely all he's got to do then is to get perl -P to call cpp -pcc ? Tom ? Hmm.. Thinking about it, perl really does need to be told about cpp flags for -P, doesn't it. Should Configure try -traditional and/or -pcc and use them if accepted ? Not that I've ever used -P, but if I ever do ... -- Ronald Khoo +44 81 991 1142 (O) +44 71 229 7741 (H)