i.e., css::uno::Any function template specializations Any::has<Any>() const Any::get(Any const &) const operator >>=(Any const &, Any &) operator <<=(Any &, Any const &) that don't make much sense (the first is always true, the rest can be replaced with operator =, which additionally supports move semantics). For 3rd-party compatibility, do this only for LIBO_INTERNAL_ONLY, however. However, some generic template code did benefit from operator >>= working also for Any, so make up for that with a new (LIBO_INTERNAL_ONLY, given that operator >>= still covers if fine for !LIBO_INTERNAL_ONLY) fromAny, complementing the existing toAny. Change-Id: I8b1b5f803f0b909808159916366d53c948206a88 Reviewed-on: https://gerrit.libreoffice.org/30022 Reviewed-by: Stephan Bergmann <sbergman@redhat.com> Tested-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.