Path: utzoo!utgpu!water!watmath!clyde!ima!haddock!karl
From: karl@haddock.ima.isc.com (Karl Heuer)
Newsgroups: comp.lang.c
Subject: Re: Portable uses of jmpbuf's
Message-ID: <9372@haddock.ima.isc.com>
Date: 12 Oct 88 20:07:22 GMT
References: <4700022@m.cs.uiuc.edu> <4700023@m.cs.uiuc.edu>
Reply-To: karl@haddock.ima.isc.com (Karl Heuer)
Organization: Interactive Systems, Boston
Lines: 18

In article <4700023@m.cs.uiuc.edu> wsmith@m.cs.uiuc.edu writes:
>I have heard that one fix is to wait for an ANSI compatible compiler which
>will allow "function(&a_jmpbuf);" and "function(jmpbuf * a);" in either case.

If you get an ANSI implementation, it will have an ANSI compatible setjmp() as
well, in which case jmp_buf will always be an array type.

In the meantime, I suggest you "fix" any implementation that gets this wrong
by changing <setjmp.h> to use an array type.  (You can always use an array of
size one, which contains the struct.)  If you can't modify <setjmp.h>, then
copy it and always include your modified copy.

ron@ron.rutgers.edu (Ron Natalie) writes:
>An extra ampersand doesn't hurt an array definition.

Yes it does.

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