14 Oct
2011
14 Oct
'11
7:24 p.m.
I wrote:
If you guys really don't think that there's
anything better to do than
that, why would you use bother to use setjmp() and longjmp()? You could
just exit().
ben wrote:
At this point, I really need to see what CPU is
running this mess.
This is the point where the 5% assembly code shows up.
There are plenty of legitimate uses for setjmp()/longjmp() that don't
require or have anything to do with use of assembly language. The whole
point of setjmp()/longjmp() is to allow unwinding the call stack in a
controlled and portable manner. Some care must be exercised to use
setjmp()/longjmp() correctly, but that is true of programming in general.