Bug 696115: Further fix for setjmp/longjmp.

Tor turned up an interesting section in the C spec about this. See
page 275 of http://open-std.org/jtc1/sc22/wg14/www/docs/n1494.pdf
regarding acceptable places for setjmp to occur.

It seems that:

  if (setjmp(buf))
  if (!setjmp(buf))
  if (setjmp(buf) {==,!=,<,>} <integer constant>)

etc are all valid things to do, but assignments (and subsequent
testing of values) like:

  if ((code = setjmp(buf)) == 0)

are not allowed.

Further, it's not even clear that:

 if (a() && setjmp(buf))

is permissible.

We therefore recast the macros into the form:

  a();
  if (setjmp((buf)) == 0)

which should be acceptable under the C spec.

To keep try atomic, we introduce a block '{{{' around this, along
with a matching close block '}}}' in the catch clause. This has the
nifty extra effect of giving us a compile time error if we mismatch
our try/catches.

0 files changed, 0 insertions, 0 deletions