Re: String literals, ASCII vs UTF-8

Eike Rathke <erack -AT- redhat.com>
Wed, 29 Feb 2012 14:48:29 +0100

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

Attachment: pgpiyTc6Wp84y.pgp
Description: PGP signature

Context

Re: String literals, ASCII vs UTF-8 (continued)

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.