Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!uakari.primate.wisc.edu!uflorida!haven!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn)
Newsgroups: comp.lang.c
Subject: Re: lseek problem
Message-ID: <11245@smoke.BRL.MIL>
Date: 7 Oct 89 02:01:11 GMT
References: <14657@uhnix1.uh.edu> <20065@mimsy.UUCP>
Reply-To: gwyn@brl.arpa (Doug Gwyn)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 21

In article <20065@mimsy.UUCP> lint@mimsy.umd.edu (The Lint Program) writes:
>In article <14657@uhnix1.uh.edu> jsmng@sysmgr.cs.uh.edu writes:
>[c code deleted]
>t.c:
>t.c(5): warning: argument argc unused in function main
>lseek, arg. 1 used inconsistently	llib-lc(90)  ::  t.c(19)
>lseek, arg. 2 used inconsistently	llib-lc(90)  ::  t.c(19)
>lseek value used inconsistently	llib-lc(90)  ::  t.c(19)
>lseek value declared inconsistently	llib-lc(90)  ::  t.c(19)
>printf returns value which is always ignored

"lint" missed some other problems:
exit() misdeclared
lseek() return comparison against NULL is wrong
fgetc() return not compared against EOF
<sys/file.h> L_SET should not be used in an application
...

"What is wrong with this program?" reminded me of the "What is wrong
with this picture?" puzzles in children's books.  Often my reaction
was, "What is RIGHT with this picture?".