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

Per,

One more comment ...

Bojsen, Per wrote:
> Hi,
>
>
> 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

johnS:
Throwing an exception is a common (and very clean) means of
aborting. This should not be prevented. One of the big
advantages of catch/throw is that you can define the abort
sequence at one location at the very top of the program
where it makes sense.

Aborting inside a single catch block tends to be a lot more
elegant than, for example, buried calls to exit(). Cleanup
and graceful exits tend to be easier from a top level
location in the program.

> 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
>

-- 
This email may contain material that is confidential, privileged
and/or attorney work product for the sole use of the intended
recipient.  Any review, reliance or distribution by others or
forwarding without express permission        /\
is strictly prohibited. If you are     /\   |  \
not the intended recipient please     |  \ /   |
contact the sender and delete        /    \     \
all copies.                      /\_/  K2  \_    \_
______________________________/\/            \     \
John Stickley                   \             \     \
Principal Engineer               \             \________________
Mentor Graphics - MED             \_
17 E. Cedar Place                   \   john_stickley@mentor.com
Ramsey, NJ  07446                    \     Phone: (201) 818-2585
________________________________________________________________