Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!rbj
From: rbj@uunet.UU.NET (Root Boy Jim)
Newsgroups: comp.lang.perl
Subject: Re: why has Cray dropped CPP support from cf77?
Message-ID: <123553@uunet.UU.NET>
Date: 22 Feb 91 03:05:21 GMT
References: <1991Feb20.190424.22590@convex.com> <1991Feb21.075334.6299@robobar.co.uk> <1991Feb21.223542.24085@convex.com>
Organization: UUNET Communications Services, Falls Church, VA
Lines: 20

In article <1991Feb21.223542.24085@convex.com> tchrist@convex.COM (Tom Christiansen) writes:
>: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 ...
>
>I don't think that cpp flags are sufficiently standardized for perl to
>infer them without help.  If not a line in Configure, maybe in the README.

Sure they are. Find a lot of systems, and pick the ones that look standard.
Convex's -pcc argument is probably bending over backwards too far.
Exactly what behavior are you preserving anyway? The ability to
substitute inside strings? Glue tokens together with /**/?
Not complain about trailing noncomments on # lines?

The cpp should have __STDC__ defined (I forget the exact symbol).
We have had sufficient warning. Now it's time to break old code.
Ship a copy of the old Reiser cpp for emergencys, if you must.
-- 
		[rbj@uunet 1] stty sane
		unknown mode: sane