Hi Stephan,
On 02/26/09 09:28, Stephan Bergmann wrote:
On 02/25/09 15:51, Mikhail Voytenko wrote:
This is of course nothing new, the discussions regarding better
error-handling design can be seen regularly. But in our case, even an
information, which exactly exception has caused the problem ( in our
scenario there is a high probability that an exception takes place )
would be helpful.
On a somewhat related note, also see
<http://qa.openoffice.org/issues/show_bug.cgi?id=94351> "pass
information about uncaught/unexpected C++ exceptions to crash reporting".
I have added a comment to the issue. This is from my point of view
another argument to have the file name and line information in the
exception.
Best regards,
Mikhail.
-Stephan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org
