From owner-cvs-all Mon Oct 21 7:46:16 2002 Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CD37437B401; Mon, 21 Oct 2002 07:46:14 -0700 (PDT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 80DA743E65; Mon, 21 Oct 2002 07:46:13 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.6/8.12.6) with ESMTP id g9LEjun4002783; Mon, 21 Oct 2002 16:46:11 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Mike Barcroft Cc: Bruce Evans , cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/i386/isa npx.c In-Reply-To: Your message of "Mon, 21 Oct 2002 10:01:36 EDT." <20021021100136.B80691@espresso.q9media.com> Date: Mon, 21 Oct 2002 16:45:56 +0200 Message-ID: <2782.1035211556@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20021021100136.B80691@espresso.q9media.com>, Mike Barcroft writes: >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 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). Well, that might be excessive. I suspect the vast majority of the "#ifdef lint" are the copyright/version strings: #ifndef lint static char const copyright[] = "@(#) Copyright (c) 1989, 1993\n\ The Regents of the University of California. All rights reserved.\n"; #endif /* not lint */ And also, while I'll admit that various standards may think of "lint" as a unreserved word in C language, various greps I've performed shows that this is actually not the case: "lint" is very much an reserved word. See our very own lint(1) for instance: [...] The lint utility runs the C preprocessor as its first phase, with the preprocessor symbol ``lint'' defined to allow certain questionable code to be altered or skipped by lint. Therefore, this symbol should be thought of as a reserved word for all code that is to be checked by lint. Considering the history of the "lint" symbol, I think we should just declare ANSI and/or POSIX in error here and treat "lint" as what it is: A well-defined reserved word. I can personally live with any particular symbol we chose... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message