> 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.
For exceptions that will only be used within a certain context, we should define it close to where it is used. For lyx-specific exceptions (what will they be?) that will be used many times, except.h is the way to go. To avoid confusion between such exceptions and the standard errors (std::logic_error etc), I usually do not use the standard ones. > But let's begin trying it out, localized in the beginning until we get a > better feeling on how it fits in. As a start, I think I can go with locally defined exceptions and std::xxx_error, until we find a need to group them into support/except.h Bo
