Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!yale!mintaka!spdcc!ima!haddock!karl
From: karl@haddock.ima.isc.com (Karl Heuer)
Newsgroups: comp.std.c
Subject: Re: why does setjmp return 1 after longjmp(buf,0)?
Message-ID: <18059@haddock.ima.isc.com>
Date: 18 Sep 90 18:01:44 GMT
References: <6511@muffin.cme.nist.gov> <13866@smoke.BRL.MIL> <4075@auspex.auspex.com>
Reply-To: karl@kelp.ima.isc.com (Karl Heuer)
Organization: Interactive Systems, Cambridge, MA 02138-5302
Lines: 8

In article <4075@auspex.auspex.com> guy@auspex.auspex.com (Guy Harris) writes:
>So it looks as if Berkeley are the ones who went off the path, here.
>Fortunately, the ANSI C spec forbids that sort of thing, so 4.4BSD

This is fortunate?  Surely a better solution would have been for ANSI to make
longjmp(buf,0) undefined behavior instead of guaranteeing the 0->1 kludge.

Karl W. Z. Heuer (karl@kelp.ima.isc.com or ima!kelp!karl), The Walking Lint