On 02/21/2012 04:07 PM, Michael Meeks wrote:
On Mon, 2012-02-20 at 09:21 +0100, Stephan Bergmann wrote:
Nice - IMHO this is all a bit silly - the 'main' has no wrapper 'catch'
around it, so if we get an un-caught exception we bomb out in a very
unpleasant way for no particularly good reason.
...
Stephan - is there a reason why we would not catch and print something
helpful (a native dialog?) on unhandled exceptions around master ?
...
In my experience, such exceptions typically indicate a programming error
(either in actual program code, or in the way the bits of the program
are combined into an installation set). And for programmers, it is
often more helpful to see the direct consequences of such error than
some "helpful" mediation on LO's part (like the infamous "The user
language cannot be determined" message, typically caused by some problem
that has zero to do with any locale data, only leading devs to start
searching in the wrong direction).
Haha :-) indeed, however a pathalogical, silent abort, without even an
auto-save, or any message from the exception is rather unfortunate
too ;-)
This should not be a "silent abort, without even an auto-save"
anyway---at least not in production builds where the sal signal handler
machinery should catch the abort. (No idea what the current status is,
which configurations lead to which behaviour wrt. that signal handler.)
Stephan
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice
