Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site brl-tgr.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!godot!harvard!seismo!brl-tgr!gwyn
From: gwyn@brl-tgr.ARPA (Doug Gwyn <gwyn>)
Newsgroups: net.lang.c
Subject: Re: setjmp(), register vars and the proposed standard
Message-ID: <5569@brl-tgr.ARPA>
Date: Thu, 1-Nov-84 23:24:47 EST
Article-I.D.: brl-tgr.5569
Posted: Thu Nov  1 23:24:47 1984
Date-Received: Sat, 3-Nov-84 07:59:26 EST
References: <4142@tekecs.UUCP>
Organization: Ballistic Research Lab
Lines: 13

> This is how the library subsection of the proposed ANSI standard
> reads for setjmp()/longjmp():
> 
> > All accessible objects have value as of the time longjmp was called,
> > except for objects of storage class auto or register whose values
> > have been changed between the setjmp and longjmp calls. These values
> > are undefined.
> 
> Given that many processors don't automatically push any kind of register
> mask on the stack (as VAXen do) this seems like a 'safe and sane' approach.

I can see the problem with registers, but why can't one count on autos
retaining their values??