Re: Anybody in US using ADA ? One silly idea..

[porton@ex-code.com (Victor Porton)]

In article <uiswpvzrh.fsf@nasa.gov>,
	Stephen Leake <Stephen.A.Leake@nasa.gov> writes:
> "Grein, Christoph" <christoph.grein@eurocopter.com> writes:
> 
>> > Which is easily solved by saying:
>> >      Lower : constant Integer := Read;
>> >      Upper : constant Integer := Read;
>> >      subtype S is Integer range Lower..Upper;
>> > 
>> > (Fortunately, declarations *are* elaborated in order :-)
>> 
>> which, by RM 3.3.1(7), is the same as
>> 
>>        Lower, Upper: constant Integer := Read;
> 
> Which is an excellent example of why declaring multiple initialized
> variables in one statement is a horrible thing to do. I'd have to
> check the manual to see if Read is called once or twice for this;
> please never do it!

So compilers need to give warnings if calling a not pure
function in a "multiple-initializer".

If we would be able to turn time back, we would to make this
an error in Ada Standard.

Oh, maybe make this an error in Ada0X despite of backward
incompatibility, as almost all these cases seem to be
erroneous or at least poorly coded (e.g. forgotten
pragma Pure).