Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!wuarchive!sdd.hp.com!elroy.jpl.nasa.gov!turnkey!itcorp!geoff
From: geoff@ITcorp.com (Geoff Kuenning)
Newsgroups: comp.sys.next
Subject: Re: strange behavior of the C preprocessor
Message-ID: <1990Oct15.074446.2887@ITcorp.com>
Date: 15 Oct 90 07:44:46 GMT
References: <9060@helios.TAMU.EDU) <9063@helios.TAMU.EDU>
Organization: Interrupt Technology Corporation, Manhattan Beach, CA
Lines: 15

In article <9063@helios.TAMU.EDU> cnh5730@calvin.tamu.edu (Chuck
Herrick) writes:

> Since Larry's patch2 requires a C preprocessor which does
> not produce this bug in order to unwrap and configure patch2,
> one wonders how one will install a patch onto the GNU 
> C preprocessor.

This is an artifact of GCC which Larry knows about.  Newer versions of
Configure use a slightly different regular expression which will
handle the inserted blank space (which is legal under the ANSI spec).
Meanwhile, the easy solution is to just modify the regular expression
in Configure by hand so that it handles blanks.
-- 
	Geoff Kuenning   geoff@ITcorp.com   uunet!desint!geoff