14 Oct
2011
14 Oct
'11
11:04 a.m.
On Fri, 14 Oct 2011, Fred Cisin wrote:
Precisely. It's the plain C analog of try / catch. Bail out of a nested
call chain without leaving a trail of if (!blah) return breadcrumbs.
--
> What is
the safe thing to do after a longjmp to a previous setjmp
> position?
On Fri, 14 Oct 2011, ben wrote:
Why the heck are you doing that?
A: Quit ... your code is toast.
It's a way to GET OUT in an unrecoverable situation, without having to
back out of all of the layers. "Go to jail. Go directly to jail. Do not
pass GO."