Re: setjmp restrictions

Article View: comp.std.c

Article #4279

#4279

From: walter briscoe
Date: Thu, 26 Oct 1995 21:48

19 lines
975 bytes

In article <814632687snz@soliton.demon.co.uk>
           ian@soliton.demon.co.uk "Ian Cargill" writes:

> The restrictions on where setjmp can be placed seem fairly 
> logical - for reasons outlined in the Rationale.  But...
> One construct that is not allowed is 
> 
> a = setjmp(buf);
> if(a)
>  . . .
> 
> Any particular reason why this might not be allowed?  I wouldn't 
> have thought it was a problem with temporaries.  

Can't answer the question. However, this construct used to fail in DEC's
VAX C 3.x.

-- 
walter briscoe

Technical Details

Message-ID: <814744121snz@wbriscoe.demon.co.uk>

Path: arc1-ca.pugleaf.net!mail2news.demon.co.uk!wbriscoe.demon.co.uk

References: <814632687snz@soliton.demon.co.uk>

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!mail2news.demon.co.uk!wbriscoe.demon.co.uk
From: walter briscoe <walter@wbriscoe.demon.co.uk>
Newsgroups: comp.std.c
Subject: Re: setjmp restrictions
Date: Thu, 26 Oct 95 21:48:41 GMT
Message-ID: <814744121snz@wbriscoe.demon.co.uk>
References: <814632687snz@soliton.demon.co.uk>
Reply-To: walter@wbriscoe.demon.co.uk
X-NNTP-Posting-Host: wbriscoe.demon.co.uk
X-Newsreader: Demon Internet Simple News v1.30

Reply to Parent Message