Re: Language lawyer question: task activation

[Georg Bauhaus <rm.tsoh.plus-bug.bauhaus@maps.futureapps.de>]

Dmitry A. Kazakov wrote:

> It neither computes nor assigns, because construction/initialization is not
> assignment. It is a different thing. The LHS object does not exist prior
> construction, but does prior assignment.
> 
>> The word "in-place" is not in Ada, only "build-in-place".
>>
>> Then, a procedure returns, too. Consequently, a
>> function returning yields a value.
> 
> What does it return? Note that it does return an object, that were illegal
> because the result is limited.

I suppose it is just a wording question: When
a function returns, there is a yield.

When a procedure P(Object: out T) returns, there
is a yield (in Object).

Assume the following language experiment:
If T is limited, we might write

   X: constant T;

begin  -- not Ada

   T'Initialize(X, Celsius => 27.3);

or some such, with the understanding that the object
named X will be provided by declaration, but will not
be initialized. Instead, it will have its initial
value when T'Initialize has returned.

Initialization is very much part of object construction in
other languages, sometimes resource management is normally
left to the implementation, too, like in Java, or Eiffel.
Can't I even control some aspects of resource
management using storage pools in constructor functions?