Xref: utzoo comp.std.c:1114 comp.sys.encore:226
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!purdue!tut.cis.ohio-state.edu!rutgers!bellcore!clyde!ima!haddock!karl
From: karl@haddock.ima.isc.com (Karl Heuer)
Newsgroups: comp.std.c,comp.sys.encore
Subject: Re: setjmp/longjmp
Keywords: setjmp, longjmp
Message-ID: <12865@haddock.ima.isc.com>
Date: 30 Apr 89 01:25:32 GMT
References: <1447@cunixc.cc.columbia.edu> <12491@ut-emx.UUCP> <39197@bbn.COM>
Reply-To: karl@haddock.ima.isc.com (Karl Heuer)
Organization: Interactive Systems, Boston
Lines: 11

In article <39197@bbn.COM> fkittred@BBN.COM (Fletcher Kittredge) writes:
>Again, this is standard behavior umong modern CPUs and Unix implementations.
>I have found this behavior in DEC, HP and Sun systems.  Both document this
>behavior, and it appears to me that ANSI C and Posix both require this
>behavior.

That's probably the wrong word; it's hard to see how a value can be "required"
to be indeterminate.  Basically, the implementation is allowed to do whatever
is most convenient if you neglect to declare such an object |volatile|.

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