office-gobmx/unotest
Stephan Bergmann 41feb036b4 Some minimal Embind support for UNO type
...which should be rare enough in practical use that it should be sufficient to
only have toString-functionality for instances mapped from C++ to JS, but no
constructor for new instances on the JS side.  (The natural choice for the
latter would be a mapping of the C++

>     inline Type( TypeClass eTypeClass, const ::rtl::OUString & rTypeName );

constructor, but which requires a mapping for the css::uno::TypeClass UNOIDL
enum, which is only provided "later" through CustomTarget_static/unoembind, so
would at least conceptually be a bit dirty.)

This Embind mapping treats css::uno::Type as a smart pointer for the underlying
typelib_TypeDescriptionReference, to benefit from the fallback garbage
collection (in more recent Emscripten versions, at least) for smart pointers,
obviating the need to call .delete() on each instance mapped to JS.

Change-Id: Ic113967c264c28641dfd1fe159012c85519f4a9b
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/164140
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann <stephan.bergmann@allotropia.de>
2024-02-29 16:19:19 +01:00
..
source Some minimal Embind support for UNO type 2024-02-29 16:19:19 +01:00
IwyuFilter_unotest.yaml
Jar_test-tools.mk
Jar_test.mk
Library_embindtest.mk Fold InternalUnoApi_embindtest into UnoApi_udkapi 2024-02-28 07:52:11 +01:00
Library_unobootstrapprotector.mk
Library_unoexceptionprotector.mk
Library_unotest.mk
Makefile
Module_unotest.mk Fold InternalUnoApi_embindtest into UnoApi_udkapi 2024-02-28 07:52:11 +01:00
README.md

Tests for UNO

Contains tests for UNO