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

[Adam Beneschan <adam@irvine.com>]

On Feb 11, 7:16 am, Robert A Duff <bobd...@shell01.TheWorld.com>
wrote:
> "Hibou57 (Yannick Duchêne)" <yannick_duch...@yahoo.fr> writes:
>
> > What a surprise to me to experience something different : limited
> > object Finalized right after Initialization.
>
> I'm not going to read your code carefully, but that doesn't
> seem right.  If you have:
>
>     X : T := F(...);
>
> the result of F is "built in place" in X, and should be finalized
> when the procedure containing X is left.

Yes, I believe that's right, and it's spelled out clearly in the RM,
in sections 7.6(17.1/3-17.11/3 and especially 17.7/3), 6.5(5.8/3),
6.5(23/2), 7.6(4), and 3.10.2(10.1/2).

P.S. That was intended as sarcasm.  I think these references are
right, but some of them contain some of the nastiest language in the
RM.  If Yannick really wants to re-check the RM, as he mentioned, I
recommend having a bottle of Tylenol handy.  Or a few beers.

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.

                                     -- Adam