Hi Stephan,
Stephan Bergmann wrote:
Kay's proposal implies that we change UNO in an incompatible way (which
would indeed affect code of the kind you mention, for example).
Originally I thought the shared-heap-string-with-a-buffer could be
introduced additionally to the standard rtl::OUString, to improve
performance critical code pieces. Unfortunately, this is not possible in
a compatible manner.
My criticism with the proposal is that it does not go far enough: If we
I only hear this seldomly :-).
ever take the big big step of changing UNO incompatibly, then instead of
exchanging one concrete implementation of rtl::OUString with a slightly
different one, we should rather investigate in replacing the concrete
implementation with an abstract interface. Behind that interface, we
can then experiment with well-tuned implementations for specific usage
scenarios (see Eike's mail for an example), without the need to become
incompatible once again.
Agreed. Just understand the proposal/analysis as being the theoretical
fundament for the construction / destruction operations of this new string.
-Stephan
Kay
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
