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

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

Adam Beneschan <adam@irvine.com> writes:

> But more simply, as I understand it: (1) When you have an extended
> return, the return object is used as the anonymous object that holds
> the function result at the point of the function call, so it's not
> finalized until the caller is done with the anonymous object; and (2)
> when the object is built in place, the anonymous object "mutates into"
> the new object and is not finalized (7.6(17.7/3)).  So yes, no
> finalization should be done until X goes out of scope.

Just to be clear: There's nothing particularly special about
extended return statements, other than the fact that they
provide a name for the result.  Build-in-place is caused
by being immutably limited, and it works fine for old-fashioned
simple return statements.  Extended return syntax can
be used with both limited and non-limited.

- Bob