Re: Returning a Struct from a Function

* James Kanze:
> On May 12, 6:59 pm, Erik Wikström <Erik-wikst...@[EMAIL PROTECTED]
> wrote:
>> On 2008-05-12 18:42, Stefan Ram wrote:
> 
>>> =?UTF-8?B?RXJpayBXaWtzdHLDtm0=?= <Erik-wikst...@[EMAIL PROTECTED]
> writes:
>>>>>> inline TwoFields ReturnMyFields(int myInt) {
>>>>>> TwoFields myReturnStruct; [...]
>>>>>> return myReturnStruct;
>>>> const TwoFields & f = ReturnMyFields(v);
> 
>>>   How long will the object created with »TwoFields
>>>   myReturnStruct;« live?
> 
>>>   I used to believe that its lifetime would end not later
>>>   than the evaluation of the full expression
>>>   »ReturnMyFields(v)« or even when the control is leaving
>>>   the block containing its declaration.
> 
>> When you bind a tem****ary to a const reference the lifetime of
>> the tem****ary is extended to last as long as the reference.
> 
> That can easily be misunderstood (and often is).  Formally, the
> rule is when the initialization expression of a reference is a
> tem****ary, the lifetime of the tem****ary is extended to
> correspond to the lifetime of that reference.  Which isn't quite
> the same thing.

Huh?

But OK, it's 25:00 o' clock for me (in the day), so perhaps not at my 
sharpest.

But explanation of difference would be appreciated, cause I can't see it.


Cheers,

- Alf

-- 
A: Because it messes up the order in which people normally read text.
Q: Why is it such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?