a8485d558f
* Client code must replace uses of idlc and regmerge with uses of unoidl-write,
see the changes to odk/examples/ and ure/source/uretext/ in
|
||
|---|---|---|
| .. | ||
| inc | ||
| source | ||
| test | ||
| tools | ||
| 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.