Since the design established thus far calls for a fixed size container and a size-constrained stack of virtual interfaces and implementation within, it is clear that more diverse parts of the type and scale handling must be forwarded into a second layer, maintained within a registry and keyed by ID. Taking the prospective use into account, a two-level structure with a fixed-size top-level index table and dynamically added extents seems to cover all requirements, and allows for a lightweight, atomic-protected read-access path.
32 lines
493 B
Text
32 lines
493 B
Text
TESTING "Library Test Suite: parameters" ./test-suite --group=param
|
|
|
|
|
|
|
|
TEST "Parameter Values" Parameter_test <<END
|
|
return: 0
|
|
END
|
|
|
|
|
|
TEST "Parameter Domain Type" ParameterDomain_test << END
|
|
return: 0
|
|
END
|
|
|
|
|
|
PLANNED "Parameter Provision" ParameterProvision_test << END
|
|
return: 0
|
|
END
|
|
|
|
|
|
TEST "Parameter value scales" ParameterScale_test << END
|
|
return: 0
|
|
END
|
|
|
|
|
|
PLANNED "Enumeration domains" NomSet_test << END
|
|
return: 0
|
|
END
|
|
|
|
|
|
PLANNED "Parameter type registry" TypeRegistry_test << END
|
|
return: 0
|
|
END
|