Date: Mon, 28 Feb 2000 01:47:13 -0800 From: "David O'Brien" <obrien@freebsd.org> To: Jim Bloom <bloom@acm.org> Cc: freebsd-current@freebsd.org, freebsd-ipfw@freebsd.org Subject: Re: cpp change breaks ipfw Message-ID: <20000228014713.A25772@dragon.nuxi.com> In-Reply-To: <38B8BAC5.9927A56E@acm.org>; from bloom@acm.org on Sun, Feb 27, 2000 at 12:48:53AM -0500 References: <38B8BAC5.9927A56E@acm.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Feb 27, 2000 at 12:48:53AM -0500, Jim Bloom wrote: > but on a new version of current this expands to > > add pass tcp from 192.168.2.5 : 255.255.254.0 to any 25 setup > > Note the extra spaces around the colon. This is required by the ANSI-C spec. Tokens replaced by `cpp' shall be seperated by white space. > There are several options here: > 1) Fix cpp to not emit the extra spaces Would break the ANSI-C spec. > 3) Document the cpp is not a valid preprocessor for ipfw on the manual page. ``cpp'' really isn't a general purpose pre-processor -- it is exclusively designed with the needs and usage of C in mind. ``m4'' is a much better general purpose processor. That said ``/usr/bin/cpp -traditional'' will do what you want it to do. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ipfw" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000228014713.A25772>