Hi Stephan, On Wednesday, 2012-02-29 08:42:35 +0100, Stephan Bergmann wrote:
> However, there are also situations where bad input (malicious or > otherwise) would cause an application to request excessive amounts > of memory to do a single task (e.g., open a document), and at least > in theory the application should be able to cope with such > externally-induced OOM conditions, by abandoning the bad operation, > cleaning up after it, telling the user the operation failed, and > carrying on. I think catching std::bad_alloc and returning an error should be possible in most filter code based on SfxObjectShell / SfxMedium. Eike -- LibreOffice Calc developer. Number formatter stricken i18n transpositionizer. GnuPG key 0x293C05FD : 997A 4C60 CE41 0149 0DB3 9E96 2F1A D073 293C 05FD
pgpBuYIfANPBj.pgp
Description: PGP signature
_______________________________________________ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
