e2451bd729
This is both an optimisation and a cleanup. This converts code like aStr.indexOf("XX") == 0 to aStr.startsWith("XX") and converts code like aStr.lastIndexOf("XXX") == aStr.getLength() - 3 to aStr.endsWith("XXX") Note that in general aStr.lastIndexOf("X") == aStr.getLength() - 1 converts to aStr.isEmpty() || aStr.endsWith("X") so I used the surrounding context to determine if aStr could be empty when modifying the code. Change-Id: I22cb8ca7c2a4d0288b001f72adb27fd63af87669 |
||
---|---|---|
.. | ||
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.