| To: | Alexander Terekhov <yyyyyyyy@xxxxxxxxxx> |
|---|---|
| Subject: | Re: XSH/XRAT conflict over cancellation points |
| From: | Wojtek Lerch <yyyyyy@xxxxxxx> |
| Date: | Fri, 21 May 2004 15:39:32 -0400 |
| Cc: | yyyyyyyyyyyyyy@xxxxxxxxxxxxx |
| References: | <OF5D5B423E.8689E5D7-ONC1256E9B.0067E20D-C1256E9B.006880EB@de.ibm.com> |
Alexander Terekhov wrote: Only if the setjmp() and longjmp() calls were generated by a disassembler. ;-)you're free to implement setjmp() in a way that will allow you to use it for exception handling.That's upside down. C compiler shall translate setjmp() macro to some magic C++ try/catch thing and longjmp() to a rather simple C+ throw. Seriously, when you're implementing a compiler, you're free to use whatever magic you find appropriate that implements the correct semantics. And C++ does not require longjmp() to have a lot of knowledge about C++ exceptions and destructors (18.7#4). |
| Previous by Date: | Re: XSH/XRAT conflict over cancellation points, Henry Spencer |
|---|---|
| Next by Date: | Re: XSH/XRAT conflict over cancellation points, Alexander Terekhov |
| Previous by Thread: | Re: XSH/XRAT conflict over cancellation points, Alexander Terekhov |
| Next by Thread: | Re: XSH/XRAT conflict over cancellation points, Alexander Terekhov |
| Indexes: | [Date] [Thread] [All Lists] |