5887aca6d1
also coverity#706033 coverity#706032 coverity#706031 coverity#706030 coverity#706029 coverity#706028 coverity#706027 coverity#706026 coverity#706025 coverity#706024 coverity#706023 coverity#706022 coverity#706021 coverity#706020 coverity#706019 coverity#706018 coverity#706017 coverity#706016 coverity#706015 coverity#706014 coverity#706013 coverity#706012 coverity#706011 coverity#706010 coverity#706009 Change-Id: I7b85e85c21cf57c9a95d3373af97593d4c3bee8f |
||
|---|---|---|
| .. | ||
| source | ||
| test | ||
| tools | ||
| workben | ||
| Executable_regcompare.mk | ||
| Executable_regmerge.mk | ||
| Executable_regview.mk | ||
| 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.