Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!sun-barr!cs.utexas.edu!usc!randvax!segue!jim
From: jim@segue.segue.com (Jim Balter)
Newsgroups: comp.unix.internals
Subject: Re: abort may return (was: Re: Checking Exit Codes)
Message-ID: <4453@segue.segue.com>
Date: 3 Nov 90 18:59:25 GMT
References: <18647@rpp386.cactus.org> <4057@awdprime.UUCP> <18658@rpp386.cactus.org> <8508@scolex.sco.COM> <18665@rpp386.cactus.org>
Reply-To: jim@segue.segue.com (Jim Balter)
Organization: Segue Software, Inc. - Santa Monica, CA. +1-213-453-2161
Lines: 13

In article <18665@rpp386.cactus.org> jfh@rpp386.cactus.org (John F. Haugh II) writes:

>i checked my 1988 X3J11 draft and it was silent

Check your eyes.  X3J11/88-001, dated January 11, 1988, page 155, section
4.10.4.1 (The abort function), last line on the page:

	The abort function cannot return to its caller.

This line also occurs in all subsequent versions of the draft, as well
as the Standard itself.

You lose, factually and conceptually.  Can we now please drop this?