Avoid -Werror=maybe-uninitialized

...as seen at least with GCC 10 trunk and --enable-optimized, when bMirroredX/Y
were used without checking that reading them with >>= had succeeded.

Assuming that in this code (added with b4a6977e05d87fe0a79b266ec30e4f403404f1b4
"tdf#129532 tdf#98839 fixes for mirror of custom shapes") it cannot be
guaranteed that rItem.Value is of the right type (so o3tl::forceAccess, which
uses assert to verify the right type, would not be appropriate), but that it is
an exception-worthy error if rItem.Value is not of the right type (so
o3tl::doAccess, which throws a css::uno::RuntimeException upon a wrong type, is
appropriate).

Change-Id: Ibe6991d69a1d6a0c2c41c839c240050a6355e98b
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/90337
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann <sbergman@redhat.com>

0 files changed, 0 insertions, 0 deletions