office-gobmx/registry
Stephan Bergmann 505fb3f952 -Werror=maybe-uninitialized
> registry/source/reflwrit.cxx: In member function ‘sal_uInt32 RegistryTypeWriter::getBlopSize()’:
> registry/source/reflwrit.cxx:1332:33: error: ‘size’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
>  1332 |     return ::getBlopSize(m_hImpl);
>       |                                 ^

at least with recent GCC 12 trunk and --enable-dbgutil --enable-optimized

Change-Id: I17abbb55ba31458147afd486a17e8455ede39b32
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/119338
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
2021-07-22 08:15:30 +02:00
..
inc
source
test
tools
CustomTarget_regcompare_test.mk
Executable_regmerge.mk
Executable_regview.mk
IwyuFilter_registry.yaml
Library_reg.mk
Makefile
Module_registry.mk
README.md
StaticLibrary_registry_helper.mk

Registry Reading, etc

This provides tools for dealing with the legacy binary types database format, still in use by extensions and the core code. While the actual binary file format is implemented by the store code, the wrapper that turns this into a type registry is implemented here.

While this code is primarily used in only two modes:

  • linear write / concatenate
  • random access read

The API unfortunately exposes a random-access write approach, which - while ~unused needs before we can re-write this away from the store backend.