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 ;-)
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.