Related articles |
---|
[4 earlier articles] |
Re: Exception Handling david.jobet@ng-market.com (David Jobet) (2002-07-25) |
Re: Exception Handling journeyman@compilerguru.com (journeyman) (2002-08-04) |
Re: Exception Handling nmm1@cus.cam.ac.uk (Nick Maclaren) (2002-08-10) |
Re: Exception Handling marcov@toad.stack.nl (Marco van de Voort) (2002-08-10) |
Re: Exception Handling max1@mbank.com.ua (Maxim Reznik) (2002-08-10) |
Re: Exception Handling fjh@cs.mu.OZ.AU (Fergus Henderson) (2002-08-14) |
Exception Handling tschirre@cs.curtin.edu.au (Bernhard Tschirren) (1998-09-13) |
Re: Exception Handling mrs@kithrup.com (1998-09-18) |
Re: Exception Handling enikitin@apk.net (1998-09-18) |
Re: Exception Handling landauer@apple.com (1998-09-18) |
Re: Exception Handling mmc@oss.dk (Morten Christensen) (1998-09-26) |
From: | Bernhard Tschirren <tschirre@cs.curtin.edu.au> |
Newsgroups: | comp.compilers |
Date: | 13 Sep 1998 22:58:50 -0400 |
Organization: | Compilers Central |
Keywords: | errors, question, comment |
Could somebody please explain "zero runtime overhead" exception handling.
Im only familiar with the traditional setjmp() / longjmp() methods.
Thanks
Bernie
[I thought the code was instrumented with a table that the exception
handler consulted to figure out which exception handler to use. -John]
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.