Stephan Bergmann
2e21240f23
O[U]StringView had an odd mixture of uses. For one, it was used like
std::[u16]string_view, for which directly using the latter std types is clearly
the better alternative. For another, it was used in concatenation sequences,
when neither of the two leading terms were of our rtl string-related types.
For that second use case introduce O[U]String::Concat (as std::[u16]string_view
can obviously not be used, those not being one of our rtl string-related types).
Also, O[U]StringLiteral is occasionally used for this, but the planned changes
outlined in the 33ecd0d5c4 "Change OUStringLiteral
from char[] to char16_t[]" commit message will make that no longer work, so
O[U]String::Concat will be the preferred solution in such use cases going
forward, too.
O[U]StringView was also occasionally used to include O[U]StringBuffer values in
concatenation sequences, for which a more obvious alternative is to make
O[U]StringBuffer participate directly in the ToStringHelper/O[U]StringConcat
machinery.
Change-Id: I1f0e8d836796c9ae01c45f32c518be5f52976622
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/101586
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
Generators for language-binding--specific representations of UNOIDL entities: - cppumaker generates header (.hdl and .hpp) files for the C++ UNO language binding - javamaker generates class files for the JVM language binding - the codemaker for .Net is in module cli_ure Some of the code is re-used by the skeletonmakers in module unodevtools. Note the different terminology used by cppumaker vs. gbuild for the three variants that can be generated by cppumaker for some of the inline functions: cppumaker switch: -L; cpputype.cxx: light; gbuild: normal; cppumaker switch: none; cpputype.cxx: normal; gbuild: bootstrap; cppumaker switch: -C; cpputype.cxx: comprehensive; gbuild: comprehensive; ...a recipe for confusion.