Date: prev next · Thread: first prev next last
2015 Archives by date, by thread · List index


https://bugs.freedesktop.org/show_bug.cgi?id=88205

            Bug ID: 88205
           Summary: Adapt uses of css::uno::Sequence to use
                    initializer_list ctor
           Product: LibreOffice
           Version: unspecified
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Libreoffice
          Assignee: libreoffice-bugs@lists.freedesktop.org
          Reporter: sbergman@redhat.com
                CC: libreoffice@lists.freedesktop.org

Since
<http://cgit.freedesktop.org/libreoffice/core/commit/?id=d79b96cf6564187c96f5a1451ca98e2c93adee77>
"css::uno::Sequence ctor with initializer_list," that class has a ctor taking a
C++11 std::initializer_list, which can greatly simplify some code constructing
Sequence instances (see the commit for some examples).

Find places in the code that would benefit from adapting them (good candidates
are "getSupportedServiceNames" functions that return statically known OUString
Sequences).

(Note that this is a LIBO_INTERNAL_ONLY feature that cannot be used in external
code though; in general, just keep away from files in include/cppu,
include/cppuhelper, include/sal, include/salhelper, include/uno, and
odk/examples.)

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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.