On 01/04/2013 08:53 AM, Noel Grandin wrote:
Why are we catching std::bad_alloc all over the place?git grep 'catch.*bad_alloc' | wc -l 68 Surely we should just let it crash? Or have a single handler for the whole process that at least attempts to provide some debugging data? At the moment, most of them just log something and then continues, which strikes me as counter-productive.
Some of the catch blocks might be (somewhat hopeless) attempts at making functions (typically those implementing UNO interface methods) adhere to their dynamic exception specifications.
Stephan _______________________________________________ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
