On Thu, Oct 25, 2012 at 10:56 AM, Michael Stahl <mstahl@redhat.com> wrote:
if we simply replace the existing String uses with OUString we don't
have to worry about that any more :)
Well, you do need to worry, if you want to enforce the language spec
(although these are pretty weak and fuzzy)
Right know we seems to care about padding of fixed-length String on
Init only (Dim)... I have not stumbled upon code that cares about that
on assign and other manipulations...
iow
Dim foo as STRING*10 = ""
dim bar as STRING "hello"
foo = bar
what should be foo? "hello" or "hello "
This is probably not a 'generaly' solvable problem as this notion of
fixed-size has been dropped post VB6.0, and now everything is var-len
with a max at 2GB. iow old and new spec conflict.
So I guess my question is: while migrating to OUString, should we care
about the corner-case and other oddities associated with 'fixed'
String.
Norbert
no leak because OUString::operator= should decrement the ref-count of
ahhh the infamous c++ operator overload... and hidden behind a layer
of good old C macros to boot :-)
Thanks for the answer.
Context
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.