> That sounds good to me. Do you want to make the edit?
Done like this:
2008-06-07 Bruno Haible <[EMAIL PROTECTED]>
* doc/posix-functions/_setjmp.texi: Explain the use of this function
regardless of POSIX.
* doc/posix-functions/_longjmp.texi: Likewise.
* doc/po
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Bruno Haible on 6/6/2008 7:28 PM:
|
| Can you then please fix the gnulib doc to not be so negative about _setjmp/
| _longjmp? I propose:
|
| A future revision of POSIX later than the 2008/2009 one may drop the
functions
| _setjmp and _lon
Eric Blake wrote:
> 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).
Sure. But that POSIX 200x draft still describes 'setjmp' as having unspecified
behaviour w.r.t. signal mask. They are calling _setjmp
-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
Eric Blake wrote:
> Meanwhile, I'm committing this (POSIX states
> that the various *setjmp are allowed to be only a macro; but *longjmp must be
> linkable functions):
Thanks for the doc fixes. Most of this symbol / platform presence/absence
matrix was generated automatically. On some macro-like
