Re: copy constructor not being called

Marcin Swiderski wrote:
> On 15 Kwi, 20:33, suresh <suresh.amritap...@[EMAIL PROTECTED]
> wrote:
>>    base b1 = 'x'; //why copy constructor not called here?
> 
> This line calls base(const char) constructor and that is the correct
> behaviour. This sytanx means that object b1 is initialized with
> value 'x'. It's equivalent to:
> 
> base b1('x');
> 


NO it isn't. The reason that the copy ctor is not called is that the
standard gives explicit permission to implementations to elide the copy
ctor in such cases and construct the 'tem****ary' in the memory set aside
for b1. However if the ctor taking a char is either explicit or private
you will find that the two syntaxes behave differently.

-- 
      [ See http://www.gotw.ca/resources/clcm.htm
for info about ]
      [ comp.lang.c++.moderated.    First time posters: Do this! ]