Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!cbatt!ihnp4!qantel!lll-lcc!lll-crg!seismo!umcp-cs!chris
From: chris@umcp-cs.UUCP (Chris Torek)
Newsgroups: net.lang.c
Subject: Re: Functions that never return
Message-ID: <3611@umcp-cs.UUCP>
Date: Fri, 26-Sep-86 18:42:56 EDT
Article-I.D.: umcp-cs.3611
Posted: Fri Sep 26 18:42:56 1986
Date-Received: Tue, 30-Sep-86 05:46:57 EDT
References: <3274@watmath.UUCP> <86900064@haddock> <3347@watmath.UUCP>
Organization: Computer Sci. Dept, U of Maryland, College Park, MD
Lines: 22

In article <3347@watmath.UUCP> rbutterworth@watmath.UUCP (Ray
Butterworth) writes:
>Exactly where would you put this "void exit(int) {for (;;);}" ?
>I imagine you mean putting it in the lint library, but if that is
>the case, lint won't see it until the second pass.  It is the first
>pass that needs to know that exit() doesn't return ....

What first pass?  What second pass?  (I know: the ones in your
implementation.  Yes, they are there in mine as well.  What does
that matter?)

Perhaps it is just a Small Matter of Programming, but at least in
an initial design phase---which is all this is likely ever to be---
one should not worry about implementation details.

[For those who have not heard the phrase, SMOP, a Small Matter of
Programming, is an ironic term attached to programming tasks that
are by no means trivial.]
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 1516)
UUCP:	seismo!umcp-cs!chris
CSNet:	chris@umcp-cs		ARPA:	chris@mimsy.umd.edu