Re: API design considerations - variable-length array in record type

[Niklas Holsti <niklas.holsti@tidorum.invalid>]

On 12-10-09 05:02 , Shark8 wrote:
> On Monday, October 8, 2012 3:03:04 AM UTC-6, Maciej Sobczak wrote:
>>
>> type R is record
>>    X : Integer;
>>    Y : Unbounded_String;
>>    Z : Array_Of_Integers_That_We_Talk_About_Here;
>> end record;
>>
>> Requirements:
>> 1 - the enclosing record type should not be limited (it should be copyable)
>> 2 - the record type can be explicitly controlled, if necessary
>> 3 - the record type should be definite (it should not require initialization)
>> 4 - it should be possible to assign to Z, just as it is possible to assign to X and Y, and the new value for Z *might have a different length* 
> 
> Why not use discriminants on the record?
> 
> Default : Constant := Natural'First;
> type R( Array_Length : Natural:= Natural'First ) is record
>    X : Integer;
>    Y : Unbounded_String;
>    Z : Array_Of_Integers_That_We_Talk_About_Here(1..Array_Length):= (Others => Default);
> end record;

Requirement 4 is not satisfied: if you assign a new value to R.Z, it has
to have the same length as the old value (R.Array_Length). You can
change the length only by assigning a new value, with the new discrimant
value, to the whole record.

And there is the memory usage problem that Adam described.

-- 
Niklas Holsti
Tidorum Ltd
niklas holsti tidorum fi
      .      @       .