Re: setjmp doc fixes

[Eric Blake]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Bruno Haible on 6/6/2008 5:53 PM:
|
| Regarding _setjmp and _longjmp you say that they are "obsolete". I disagree
| for two reasons:

I was going off of the POSIX 200x draft copy, where they were given OB
shading (ie. a future version of POSIX may withdraw support for them).

I have no disagreements that _setjmp is still the only documented way to
save context without wasting time on signal masks, nor that it is likely
faster than sigsetjmp(,0).  Rather, the question (which you should
probably take up with the Austin group) is whether bypassing the signal
mask is safe enough to keep without obsoletion, and in which use cases.
It is certainly NOT safe for use in signal handlers.

- --
Don't work too hard, make some time for fun as well!

Eric Blake             address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkhJ0ZkACgkQ84KuGfSFAYA0fQCgsB7g5k4w7r3JGCASWSiXteAC
nBYAn00FR/akkAKn8tCaYZsxPhRQEyyS
=wFu0
-----END PGP SIGNATURE-----