Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 (Tek) 9/26/83; site tekecs.UUCP
Path: utzoo!linus!decvax!tektronix!orca!tekecs!peterg
From: peterg@tekecs.UUCP
Newsgroups: net.lang.c
Subject: setjmp(), register vars and the proposed standard
Message-ID: <4142@tekecs.UUCP>
Date: Tue, 30-Oct-84 12:59:54 EST
Article-I.D.: tekecs.4142
Posted: Tue Oct 30 12:59:54 1984
Date-Received: Thu, 1-Nov-84 04:10:38 EST
Sender: peterg@tekecs.UUCP
Organization: Tektronix, Wilsonville OR
Lines: 14

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.


UUCP:	...!{ucbvax or decvax}!tektronix!tekecs!peterg
ARPA:	tekecs!peterg.tektronix @ udel-relay