It was strange to realize that both AADL_Project and Modeling_Properties property sets (which both are predeclared ones) contain Size_Range type declaration. This fact itself gives some uncertainty.
What wonders more is that these two definitions are different: one is a range of Size (which in its turn is an integer with units of information amount) and the second one is just a range of integers. In Modeling_Properties property set it is used only for the property named Acceptable_Array_Size which definition seems to be consistent to the definition of "just a range of integers" while the rest of the standard uses Size_Range in the meaning of "range of integers with information amount unit".
So, I would like to consider Size_Range to be defined only in the AADL_Project property set and Acceptable_Array_Size to be defined as list of range of aadlinteger.
Probably, for v3 we should consider a better name for a value with information amount unit rather than `Size' due to its ambiguity.
It was strange to realize that both
AADL_Project
andModeling_Properties
property sets (which both are predeclared ones) containSize_Range
type declaration. This fact itself gives some uncertainty.What wonders more is that these two definitions are different: one is a
range
ofSize
(which in its turn is aninteger
with units of information amount) and the second one is just arange
ofinteger
s. InModeling_Properties
property set it is used only for the property namedAcceptable_Array_Size
which definition seems to be consistent to the definition of "just a range of integers" while the rest of the standard usesSize_Range
in the meaning of "range of integers with information amount unit".So, I would like to consider
Size_Range
to be defined only in theAADL_Project
property set andAcceptable_Array_Size
to be defined aslist of range of aadlinteger
.Probably, for v3 we should consider a better name for a value with information amount unit rather than `Size' due to its ambiguity.