On Fri, 2012-03-02 at 16:00 +0100, Stephan Bergmann wrote:
And when/if we replace the sal C API with a C++ one in LO 4 (where a
memory allocation function, if we would still need a home-grown one
anyway, would naturally throw bad_alloc)
Yeah, back the O[UString contents with direct new/delete calls in a real
implementation body instead of current thin header-only wrapper around
the C-API which backs onto rtl_allocateMemory/rtl_freeMemory.
Alternative, replace rtl_allocateMemory/rtl_freeMemory in strtmpl.cxx
with new/delete, and remove the inline bad_alloc throwing from the
header and assume that there isn't any existing users of the c-api that
ever checked that rtl_uString2String failed
C.
Context
- Re: String literals, ASCII vs UTF-8 (continued)
Exception cost on string allocations ... · Michael Meeks
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.