Re: why does setjmp return 1 after longjmp(buf,0)?

Article View: comp.std.c

Article #1731

#1731

From: Guy Harris
Date: Wed, 19 Sep 1990 17:52

12 lines
896 bytes

>>Fortunately, the ANSI C spec forbids that sort of thing, so 4.4BSD
>
>This is fortunate?

It's fortunate that ANSI C is saying *something* about the subject, so
that vendors know what they must do and implementors know what they can
count on.

I don't particular care *what* they say; just about anything will work
without too much pain, I don't ever pass "longjmp" a second argument of
0 anyway, and if something that's not ideal in the technical sense is
necessary to get consensus, I can live with it.

Technical Details

Message-ID: <4079@auspex.auspex.com>

Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!auspex!guy

References: <13866@smoke.BRL.MIL> <4075@auspex.auspex.com> <18059@haddock.ima.isc.com>

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!auspex!guy
From: guy@auspex.auspex.com (Guy Harris)
Newsgroups: comp.std.c
Subject: Re: why does setjmp return 1 after longjmp(buf,0)?
Message-ID: <4079@auspex.auspex.com>
Date: 19 Sep 90 17:52:49 GMT
References: <13866@smoke.BRL.MIL> <4075@auspex.auspex.com> <18059@haddock.ima.isc.com>
Organization: Auspex Systems, Santa Clara
Lines: 12

Reply to Parent Message