Stephan Bergmann wrote: > One abstraction level higher, throwing an exception upon detecting say a > broken invariant is in general useful only if you very carefully > designed your program so that you can catch the exception somewhere > where you can go from the broken state of your program to a good state > (and where you can inform the client that some operation failed, if the > good state is not a state expected by the client).
While this might be theoretically correct my practical experience of at least 8 years of successful crash recovery says that it works for the vast majority of crashes and I won't accept that we drop it in any situation just because there is no theoretical proof that it works all the time. I would see it the other way around: only if you have a case where you know for sure that crash recovery is of no avail you can abort immediately (but then you will also lose the crash report). Ciao, Mathias -- Mathias Bauer - OpenOffice.org Application Framework Project Lead Please reply to the list only, [EMAIL PROTECTED] is a spam sink. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
