Re: Ranges and (non)static constraints

[Maciej Sobczak <no.spam@no.spam.com>]

Martin Krischik wrote:
> 
> On 16 Nov., 12:02, Maciej Sobczak <no.s...@no.spam.com> wrote:
>> Hi,
>>
>> type T is range 1 .. N;
>> type U is new Integer range 1 .. M;
>>
>> N must be static, but M does not have to.
>> Why and what is the real difference between T and U?
> 
> Let me answer with a question: What value has T'Size?

Whatever the compiler picks to fit the given range? :-)

OK, now I see - but is there any preference I should give to one of 
these two forms apart from that? I understand that the second form is 
the only I can use if the range is not statically known and (what 
surprised me) when the constraints come from formal generic parameters.
But even if the range is known statically, I might choose to always use 
the second form for notational consistency. Is this recommended?

Assuming that T'Size = U'Size, can I expect any run-time observable 
(including performance) differences between T and U?

-- 
Maciej Sobczak : http://www.msobczak.com/
Programming    : http://www.msobczak.com/prog/