«

On 10/28/10 05:18 PM, Ian Collins wrote:
> On 10/28/10 05:10 PM, cronusf wrote:
>>
>> std:stream& operator<<(std:stream& os, Complex& c)
>> {
>> os<< "("<< c.real<< ", "<< c.imag<< ")"<< std::endl;
>>
>> return os;
>> }
>>
>> int main()
>> {
>> Complex c1(1.0f, 2.0f);
>> Complex c2(1.0f, 2.0f);
>>
>> std::cout<< c1 + c2<< std::endl;
>> }
>>
>> Output: (2, 4)
>
> That shouldn't compile. There isn't a suitable operator << for Complex.

Which probably means that compiler doesn't enforce the can't bind a
temporary to a non const reference rule. So what you see is compiler,
rather than language specific.

--
Ian Collins

* Ian Collins, on 28.10.2010 06:30:
> On 10/28/10 05:18 PM, Ian Collins wrote:
>> On 10/28/10 05:10 PM, cronusf wrote:
>>>
>>> std:stream& operator<<(std:stream& os, Complex& c)
>>> {
>>> os<< "("<< c.real<< ", "<< c.imag<< ")"<< std::endl;
>>>
>>> return os;
>>> }
>>>
>>> int main()
>>> {
>>> Complex c1(1.0f, 2.0f);
>>> Complex c2(1.0f, 2.0f);
>>>
>>> std::cout<< c1 + c2<< std::endl;
>>> }
>>>
>>> Output: (2, 4)
>>
>> That shouldn't compile. There isn't a suitable operator << for Complex.
>
> Which probably means that compiler doesn't enforce the can't bind a temporary to
> a non const reference rule. So what you see is compiler, rather than language
> specific.

Yes, "cronusfh" is using Visual C++ 8.

Presumably he's ignoring the warning about non-standard language extension being
used.

Cheers,

- Alf

--
blog at <url: http://alfps.wordpress.com>

On 27 Okt., 03:36, cronusf wrote:
> Suppose I have a class Complex and I overload operator double()
> to get the real part.

I would consider this a /misuse/ of operator overloading. Try to
avoid "lossy" user-defined implicit conversions. Here, the resulting
double value won't properly represent the value of the original
complex object in general. Make the user explicitly say what he/she
intends to do to avoid any accidental data losses.

Cheers!
SG