office-gobmx/registry
Thomas Arnhold 5bb4a2ba1d further OUString cleanup
Change-Id: I19954ee5976cb881a5fe73a889c8e04a19b14eb6
2013-03-19 14:18:10 +01:00
..
inc/registry cleanup doxygen warnings 2013-03-18 21:57:02 -04:00
source removal of RTL_CONSTASCII_USTRINGPARAM for quoted OUStrings declarations 2013-03-19 10:48:30 +00:00
test
tools
util
workben further OUString cleanup 2013-03-19 14:18:10 +01:00
Executable_regcompare.mk
Executable_regmerge.mk
Executable_regview.mk
Library_reg.mk
Makefile
Module_registry.mk
README
StaticLibrary_registry_helper.mk
ZipPackage_registry_odk_headers.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.