C++ Exceptions from SCE-MI Error and/or Info Handler?

Hi,

the Routed example in the SCE-MI standard installs a custom SCE-MI
error handler which throws a C++ exception. The SCE-MI standard
says nothing regarding whether this is allowed or not. However,
for this to work, the application must be able to wrap an exception
handler around every call chain that can cause a SCE-MI error
to happen. This may not always be possible because the application
may employ various callbacks or UNIX signal handlers for instance.
These will typically run in a different context and with a different
callchain so may not be protected by the user's exception handler.
This will lead to the error either not being visibly reported or
segmentation faults or other bad behavior.

I'd like to solicit the committee's comments on this issue. At a
minimum I think the Routed example should follow the SCE-MI standard's
recommendation (or is it even a mandate) that the error handler should
abort rather than throw an exception. Or do we want to allow this
use model? In that case, the standard should be modified to explicitly
state so as this has implementation consequences.

Thanks,
Per

Per Bojsen
Zaiq Technologies
Received on Thu May 27 08:51:56 2004