office-gobmx/registry
Tor Lillqvist 6ad127ead7 tdf#127766: Avoid ODR violation for class/struct FieldEntry
We had a class FieldEntry in registry/source/reflwrit.cxx and a struct
FieldEntry in sd/source/filter/eppt/text.hxx. That causes problems
when code from both is linked into one binary, as in the iOS and
Android apps. The wrong FieldEntry destructor got called from the code
in sd which of course lead to a crash.

Fix by putting the one in registry into an unnamed namespace. (I put a
large chunk of the source file in it while at it.)

Change-Id: I1b32075f7aba256129b36ceb38eba605c882b9ff
Reviewed-on: https://gerrit.libreoffice.org/80141
Tested-by: Jenkins
Reviewed-by: Tor Lillqvist <tml@collabora.com>
2019-10-03 17:35:37 +02:00
..
inc
source tdf#127766: Avoid ODR violation for class/struct FieldEntry 2019-10-03 17:35:37 +02:00
test
tools
CustomTarget_regcompare_test.mk
Executable_regmerge.mk Add version resource to executables where it was missing 2019-08-31 00:22:28 +02:00
Executable_regview.mk Add version resource to executables where it was missing 2019-08-31 00:22:28 +02:00
IwyuFilter_registry.yaml
Library_reg.mk
Makefile
Module_registry.mk
README
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.