Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 alpha 4/15/85; site ucbvax.ARPA
Path: utzoo!watmath!clyde!bonnie!akgua!whuxlm!whuxl!houxm!mhuxt!mhuxr!ulysses!ucbvax!info-vax
From: info-vax@ucbvax.ARPA
Newsgroups: fa.info-vax
Subject: Re: Lint for VAX/VMS C
Message-ID: <7693@ucbvax.ARPA>
Date: Sun, 2-Jun-85 01:15:43 EDT
Article-I.D.: ucbvax.7693
Posted: Sun Jun  2 01:15:43 1985
Date-Received: Mon, 3-Jun-85 06:07:32 EDT
Sender: daemon@ucbvax.ARPA
Organization: University of California at Berkeley
Lines: 18

From: Jon L. Spear <JSPEAR@MIT-MC.ARPA>

The question of lint for VMS C came up at DECUS last week, and DEC's reply was
that they had no plans at this time to provide a lint.  Their reasons were

1) VMS C already has much better diagnostics than most other C compilers, and
they plan to enhance dignostics further in future releases, thus the nead for 
lint is much reduced.

2) The proposed ANSI C will probably require compiler checks similar to those
in VMS C, and includes many other changes that would obviate many lint
features, thus if they ever decide to provide lint or some other static
analysis tool, they will probably wait until the C standard matures.

(these are my recollections only, and as a non-C hacker, my ear was not tuned
to this frequency)

-Jon