Yes, some CPP instances could be useful in the context of a method where the object is no longer needed after the method returns, so thats a good point to add.

Perhaps 'not compatible' was a poor choice of words on my part. My point was that NS_HANDLER is expecting an NSException and won't see a std:exception and it would throw past the handler code. The converse could also happen and neither would unwind as expected. But the wrapper shows an approach for translation between them.

setjump/longjmp; std:exception and NSException can all be used in the same application, they just need to be used with care.