"Bo Peng" <[EMAIL PROTECTED]> writes:
| Dear list,
|
| I get used to try/catch/throw for error handling and find it difficult
| to write code without them. What is the current coding rule regarding
| exception? If we are starting to use them, does it make sense to add a
| except.h and define all exceptions (such as lyx::err_empty_whatever)
| over there?
I think that none of use "regulars" are really experienced in using
exceptions. OTOH I at least has read quite a lot about how to write
exception safe code.
I am not sure if a except.h is the right way to go, but it might be.
But initially I think that the exception definitions used should stay
close to the classes/functions that use them. And we should try to
avoid creating an overly complex exception hierarchy. But let's begin
trying it out, localized in the beginning until we get a better
feeling on how it fits in.
Would that be ok with you?
--
Lgb
