Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site kitty.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!rochester!rocksanne!sunybcs!kitty!peter
From: peter@kitty.UUCP (Peter DaSilva)
Newsgroups: net.bugs.usg
Subject: Re: "lint" lets very bad code pass
Message-ID: <189@kitty.UUCP>
Date: Wed, 31-Jul-85 11:06:33 EDT
Article-I.D.: kitty.189
Posted: Wed Jul 31 11:06:33 1985
Date-Received: Fri, 2-Aug-85 08:15:44 EDT
References: <2454@sun.uucp>
Distribution: net
Organization: Recognition Research Corp., Clarence, NY
Lines: 19

> For those of you who realize why the code that earlier "lint"s complained
> about is bad, you can make the System V "lint" complain too by deleting the
> two lines that read
> 
> 		if( sizeof(int) == sizeof(long) && !pflag ) return( 0 );
> 
> from the routine "chktype" in "lpass2.c".  This line was *not* present in
> earlier "lint"s, and is the culprit.  (One should *NOT* have to specify the
> "-p" flag - which checks for portability to various non-UNIX implementations
> of C - in order to get it to check for a bug which impairs portability to
> perfectly good UNIX C implementations.)
> 
> 	Guy Harris

Portability is portability. This is the first time I've heard that lint only
checks for portability to non-UNIX systems. The documentation refers to the
GCOS & IBM dialects of 'C'. Since UNIX runs on IBM mainframes shouldn't it
complain about such things as "if(c<'0')", since this isn't portable to
certain UNIX systems?