office-gobmx/registry
David Tardon 9f68316127 fix linkage inconsistency on windows
Change-Id: I677a5fe8dc5c91b96fe299b06a5f2dc767120a1d
2012-05-06 08:19:43 +02:00
..
inc/registry fix linkage inconsistency on windows 2012-05-06 08:19:43 +02:00
prj gbuild conversion: registry module 2012-05-06 07:23:20 +02:00
source fix linkage inconsistency on windows 2012-05-06 08:19:43 +02:00
test Replaced a few equal calls with == 2012-04-08 19:24:00 +02:00
tools gbuild conversion: registry module 2012-05-06 07:23:20 +02:00
util gbuild conversion: registry module 2012-05-06 07:23:20 +02:00
workben remove include of pch header from registry 2011-11-27 13:16:40 -06:00
Executable_checksingleton.mk gbuild conversion: registry module 2012-05-06 07:23:20 +02:00
Executable_rdbedit.mk gbuild conversion: registry module 2012-05-06 07:23:20 +02:00
Executable_regcompare.mk gbuild conversion: registry module 2012-05-06 07:23:20 +02:00
Executable_regmerge.mk gbuild conversion: registry module 2012-05-06 07:23:20 +02:00
Executable_regview.mk gbuild conversion: registry module 2012-05-06 07:23:20 +02:00
Library_reg.mk gbuild conversion: registry module 2012-05-06 07:23:20 +02:00
Makefile gbuild conversion: registry module 2012-05-06 07:23:20 +02:00
Module_registry.mk gbuild conversion: registry module 2012-05-06 07:23:20 +02:00
Package_inc.mk gbuild conversion: registry module 2012-05-06 07:23:20 +02:00
README more documentation and cleanups for various modules. 2012-03-06 16:29:23 +00:00
StaticLibrary_registry_helper.mk gbuild conversion: registry module 2012-05-06 07:23:20 +02:00
version.mk changefileheader2: #i109125#: change source file copyright notice from Sun Microsystems to Oracle; remove CVS style keywords (RCSfile, Revision) 2010-02-12 15:01:35 +01:00

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.