On Fri, 2012-09-28 at 13:46 +0200, Noel Grandin wrote:
Hi
I don't really understand the point of not being able to mutate OUString
in-place, but being able to overwrite it via the assignment operator?
It seems to me it should be one or the other.
Either OUString is immutable, and it cannot be assigned to, except via a
constructor, or it is mutable, and we can pretty much throw away
OUStringBuffer.
Consider OUString as a smart const pointer to an immutable rtl_uString.
i.e.
const char *pFoo;
pFoo = "hello";
pFoo = "world"; //ok
pFoo[0] = 'A'; //won't compile
const_cast<char*>(pFoo)[0] = 'A'; //compiles but evil
C.
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.