office-gobmx/registry
Noel Grandin c82efb610b clang-tidy modernize-concat-nested-namespace
Change-Id: Iab35a8b85b3ba1df791c774f40b037f9420a071a
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/86708
Tested-by: Jenkins
Reviewed-by: Noel Grandin <noel.grandin@collabora.co.uk>
2020-01-31 18:36:09 +01:00
..
inc
source sal_Char->char in oox..registry 2019-12-19 19:17:40 +01:00
test sal_Char->char in oox..registry 2019-12-19 19:17:40 +01:00
tools clang-tidy modernize-concat-nested-namespace 2020-01-31 18:36:09 +01:00
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.