Date: Mon, 21 Oct 2002 10:01:36 -0400 From: Mike Barcroft <mike@FreeBSD.org> To: Poul-Henning Kamp <phk@critter.freebsd.dk> Cc: Bruce Evans <bde@zeta.org.au>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/i386/isa npx.c Message-ID: <20021021100136.B80691@espresso.q9media.com> In-Reply-To: <2283.1035208541@critter.freebsd.dk>; from phk@critter.freebsd.dk on Mon, Oct 21, 2002 at 03:55:41PM %2B0200 References: <20021021093912.A80691@espresso.q9media.com> <2283.1035208541@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
Poul-Henning Kamp <phk@critter.freebsd.dk> writes: > In message <20021021093912.A80691@espresso.q9media.com>, Mike Barcroft writes: > > >Can your lint define a constant that is in the implementation > >namespace (eg. _LINT)? This would at least improve your change to > >i386's <machine/_types.h> which breaks things if an application > >happens to `#define lint' in a C90 environment. > > Ohh, absolutely, that would be no problem at all. > > The problem is that "lint" is our standard for this: > > bang# sh /root/gsys lint | grep '#' | grep -v compile | wc -l > 299 > bang# sh /root/gsrc lint | grep '#' | grep -v compile | wc -l > 5558 > > I'm not particularly attached to "lint", it can be any symbol we > decide on, as long as we use the same one all over... Yes, but this is the second time ever "lint" has been used in a standard header or in a header a standard header includes. The first was in <sys/cdefs.h> about a month ago, but since it only modifies macros in the implementation namespace it isn't a problem. It might be a wise idea to do a mass rename (similar to the KERNEL to _KERNEL mass rename of 1999). Best regards, Mike Barcroft To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021021100136.B80691>