Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!cornell!rochester!uhura.cc.rochester.edu!ur-valhalla!badri
From: badri@valhalla.ee.rochester.edu (Badri Lokanathan)
Newsgroups: comp.lang.c
Subject: Re: Strange lint mumblings
Summary: Will not clean up automatically.
Message-ID: <1700@valhalla.ee.rochester.edu>
Date: 27 Dec 88 22:12:15 GMT
References: <416@marob.MASA.COM> <11467@dartvax.Dartmouth.EDU> <179@amsdsg.UUCP> <599@micropen>
Organization: UR Dept. of Electrical Engg, Rochester NY 14627
Lines: 18

In article <599@micropen>, dave@micropen (David F. Carlson) writes:
> I have solved this "problem" by not using the function exit() to return
> to the calling environment main() status.  Rather, use return at the end
> of main().  Lint seems to like return from functions.  It never has been
> able to deal with exit() properly, ("statement not reached", etc.) so why 
> try?
> 
Alas, some of us (at least I) have gotten used to the easy clean up facility
that exit() provides. That is, flushing all I/O buffers and closing
them. return(status) works cleanly if the programmer takes care of
this. I have personally not had this problem with return/exit in lint, so I
shall continue to use exit (maybe I should use egress as PT Barnum once
did :-)
-- 
"I care about my fellow man              {) badri@ee.rochester.edu
 Being taken for a ride,                //\\ {ames,cmcl2,columbia,cornell,
 I care that things start changing     ///\\\ garp,harvard,ll-xn,rutgers}!
 But there's no one on my side."-UB40   _||_   rochester!ur-valhalla!badri