Re: Initialization and Finalization of limited object "returned" by a function

[Robert A Duff <bobduff@shell01.TheWorld.com>]

"Hibou57 (Yannick Duch�ne)" <yannick_duchene@yahoo.fr> writes:

> Clarification about my words : what I've quoted from you, was talking
> about extended return statement. I was understanding this as "extended
> return statement applied to limited".

Extended return statements are not much more than syntactic sugar.  They
don't change anything about when the result object is finalized.  All
they do is give you a name you can use to refer to the result object.
If there's no name, the result object is still there, but you can't
refer to it inside the function body.

Oh, I guess there's one other thing extended returns do -- they
allow you to default-initialize the result object:

    return X : T;

which can't be expressed with a simple return.

Extended return statements are important in the limited case,
because you often want to say something like "Result.X := ...;".
And as you discovered, aggregates aren't allowed for protected
or task types (which was probably a language design mistake).

Extended return statements are not so important for nonlimited types,
but they do come in handy in that case, too.

- Bob