Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!bfmny0!tneff
From: tneff@bfmny0.UU.NET (Tom Neff)
Newsgroups: comp.lang.c
Subject: Re: Warning messages
Keywords: large projects
Message-ID: <15102@bfmny0.UU.NET>
Date: 20 Jan 90 01:22:52 GMT
References: <1471@mdbs.UUCP> <2NNQZ%@rpi.edu> <25AFE8A6.14024@paris.ics.uci.edu> <15673@haddock.ima.isc.com>
Reply-To: tneff@bfmny0.UU.NET (Tom Neff)
Lines: 12

In article <15673@haddock.ima.isc.com> karl@haddock.ima.isc.com (Karl Heuer) writes:
>$ If you say that the solution is to use |return| instead of |exit()|, I can't
>  accept that.  Both are correct, the arguments for one are about as good as
>  for the other, and it's not the sort of thing that the compiler should try
>  to enforce.

Just use both.

It executes the way you want, and parses the way C wants.
-- 
"Take off your engineering hat   = "The filter has      | Tom Neff
and put on your management hat." = discreting sources." | tneff@bfmny0.UU.NET