how long can a temporary object live?

[Jess]

Hello,

If a function's signature is:

T f();

and it returns its result (of type T) by value, then the result will
be copied into a temporary place, as a temporary object. If it is a
temporary object, then can I still call T's function "g" like the
following?

(f()).g()

I'm wondering how long a temporary object can live, so that I can
modify its states via "g", or do some even more complicated operations
on this temporary object.

Thanks,
Jess

[jg]

On May 3, 8:02 pm, Jess <[e-mail]:

Hello,

If a function's signature is:

T f();

and it returns its result (of type T) by value, then the result will
be copied into a temporary place, as a temporary object. If it is a
temporary object, then can I still call T's function "g" like the
following?

(f()).g()

Definitely. The temporary for the return value is valid in the
calling context.
However, if you don't assign f() to a variable, it will be
inaccessible, thus
no use at all.

>
I'm wondering how long a temporary object can live, so that I can
modify its states via "g", or do some even more complicated operations
on this temporary object.

T t = f();
Use t to perform your operations as long as t is live.

JG

[Jim Langston]

"Jess" <wd***@hotmail.comwrote in message
news:11*********************@h2g2000hsg.googlegrou ps.com...

Hello,

If a function's signature is:

T f();

and it returns its result (of type T) by value, then the result will
be copied into a temporary place, as a temporary object. If it is a
temporary object, then can I still call T's function "g" like the
following?

(f()).g()

I'm wondering how long a temporary object can live, so that I can
modify its states via "g", or do some even more complicated operations
on this temporary object.

Yes, and it's most useful I've found for passing built up character arrays
to a C function expectign a c style string.

somefunctionexpectingcstr( (std::string("The data text is :") + datapointer
+ ":").c_str() );
or some such when I find it more meaningful to build the string in the
function parm for whatever reason.

I acutally use very similar to some graphic display of text that expects a C
string.

[Jess]

Thanks! Jess

On May 4, 1:23 pm, jg <[e-mail]:

On May 3, 8:02 pm, Jess <[e-mail]:

Hello,

If a function's signature is:

T f();

and it returns its result (of type T) by value, then the result will
be copied into a temporary place, as a temporary object. If it is a
temporary object, then can I still call T's function "g" like the
following?

(f()).g()

Definitely. The temporary for the return value is valid in the
calling context.
However, if you don't assign f() to a variable, it will be
inaccessible, thus
no use at all.

I'm wondering how long a temporary object can live, so that I can
modify its states via "g", or do some even more complicated operations
on this temporary object.

T t = f();
Use t to perform your operations as long as t is live.

JG

[James Kanze]

On May 4, 5:02 am, Jess <[e-mail]:

If a function's signature is:

T f();

and it returns its result (of type T) by value, then the result will
be copied into a temporary place, as a temporary object. If it is a
temporary object, then can I still call T's function "g" like the
following?

(f()).g()

I'm wondering how long a temporary object can live, so that I can
modify its states via "g", or do some even more complicated operations
on this temporary object.

There are a few special cases where the lifetime is extended,
but normally, the lifetime of a temporary is until the end of
the full expression in which it was constructed. So things like
f().g() are no problem (supposing, of course, that T has a
member function g()).

--
James Kanze (GABI Software) email:ja*********@gmail.com
Conseils en informatique orientée objet/
Beratung in objektorientierter Datenverarbeitung
9 place Sémard, 78210 St.-Cyr-l'École, France, [phone]