Xref: utzoo comp.lang.misc:2456 comp.lang.c:15253 comp.lang.c++:2356
Path: utzoo!utgpu!attcan!uunet!lll-winken!lll-lcc!ames!mailrus!ncar!tank!paideia!vevea
From: vevea@paideia.uchicago.edu (Jack L. Vevea)
Newsgroups: comp.lang.misc,comp.lang.c,comp.lang.c++
Subject: Re: Yet Another Lint Foul-up
Keywords: Idle curiosity.
Message-ID: <1298@tank.uchicago.edu>
Date: 6 Jan 89 08:09:25 GMT
Sender: news@tank.uchicago.edu
Reply-To: vevea@paideia.UUCP (Jack L. Vevea)
Organization: University of Chicago Department of Education
Lines: 13
References:


	I've passively watched the discussion of lint's problems with
  exit(0) from main(), and find myself wondering why it matters.  I use
  lint to check my code, but I've gotten into the habit of automatically
  ignoring certain output, including 'warning:  main() returns a random
  value to the invocation environment.'  Being primarily a psychometrician,
  and not a professional C (or any other language) programmer, I find myself
  wondering if some of you out there are working under conditions in which
  some higher authority requires you to produce a clean lint run as 
  evidence of good coding.  Otherwise, it would seem to me that any
  concern with the message would be evidence of your being a slave to
  lint; why else be concerned when you _know_ that the warning is
  inconsequential?