Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!bbn!papaya.bbn.com!rsalz
From: rsalz@bbn.com (Richard Salz)
Newsgroups: comp.unix.questions,comp.lang.c
Subject: Re: lint and volatile and const constructs
Message-ID: <186@papaya.bbn.com>
Date: Mon, 21-Sep-87 17:53:42 EDT
Article-I.D.: papaya.186
Posted: Mon Sep 21 17:53:42 1987
Date-Received: Wed, 23-Sep-87 00:47:07 EDT
References: <832@ektools.UUCP>
Reply-To: rsalz@bbn.com (Rich Salz)
Organization: BBN Laboratories, Cambridge MA
Lines: 17
Keywords: lint volatile const c updating
Xref: mnetor comp.unix.questions:4200 comp.lang.c:4471

In comp.unix.questions (<832@ektools.UUCP>), jim@ektools.UUCP (James Hugh Moore) writes:
>...  The Tektronix
>software supports const and volatile declarations for data.  Well lint 
>complains bitterly about these...

The easiest thing to do is to take advantage of the fact that "lint"
essentially puts a "#define lint" at the start of all your files.
So find some system-wide header file (e.g., /usr/cross-compiler/stdio.h?),
and add these lines to it:
	#ifdef	lint
	#define const		/* Until we get an ANSI-lint... */
	#define volatile	/* Until we get an ANSI-lint... */
	#endif	/* lint */

Put similar wrappers around your function prototypes.
-- 
For comp.sources.unix stuff, mail to sources@uunet.uu.net.