[lnkForumImage]
TotalShareware - Download Free Software
Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Forums >

comp.lang.c++

Template copy constructor question.

ravajappa.gouda@gmail.com

11/29/2008 11:16:00 AM

Hi! Can somebody tell me when does copy constructor 1 or 2 gets called
in a template class below? And if you can explain the difference
between the 1 and 2 below would be great?


template<typename T, size_t size>
class container {

public:
container() //default constructor.
{
}

template<typename cT, size_t cs> // Copy
constructor 1
container(const container<cT, cs>& rhs)
{
........
}

container(const container& rhs) // Copy
constructor 2
{
...........
}


private: ..... //
private members defined here.
};
5 Answers

peter koch

11/29/2008 12:15:00 PM

0

On 29 Nov., 12:16, "ravajappa.go...@gmail.com"
<ravajappa.go...@gmail.com> wrote:
> Hi! Can somebody tell me when does copy constructor 1 or 2 gets called
> in a template class below? And if you can explain the difference
> between the 1 and 2 below would be great?
>
> template<typename T, size_t size>
> class container {
>
> public:
>   container()   //default constructor.
>   {
>   }
>
>   template<typename cT, size_t cs>                    // Copy
> constructor 1
>   container(const container<cT, cs>& rhs)
>   {
>       ........
>   }
>
>   container(const container& rhs)                        // Copy
> constructor 2
>   {
> ..........
>   }
>
> private: .....                                                             //
> private members defined here.
>
>
>
> }
The second constructor is the default copy-constructor and will be
called whenever a normal copy constructor would normally be called.
The first one will be called in the other cases - that is if cT is
different from T or cs is different from size.
You do need the second constructor if it behaves differently from what
the compiler would generate: the templated copy constructor will never
be a substitute for the default constructor and thus you need to
supply it.

/Peter

Andrey Tarasevich

11/29/2008 9:03:00 PM

0

ravajappa.gouda@gmail.com wrote:
> Can somebody tell me when does copy constructor 1 or 2 gets called
> in a template class below?

This question is already incorrect by itself. There's only one copy
constructor in your class. It is constructor 2. Template 1 does not
define any copy constructors. It can be used to generate _conversion_
constructors, but not copy constructors.

> And if you can explain the difference
> between the 1 and 2 below would be great?

I don't really see what needs to be explained here. These constructors
take arguments of different types. So the right one will be chosen
depending on the type of the argument used during construction. That's
basically it.

> template<typename T, size_t size>
> class container {
>
> public:
> container() //default constructor.
> {
> }
>
> template<typename cT, size_t cs> // Copy
> constructor 1
> container(const container<cT, cs>& rhs)
> {
> ........
> }
>
> container(const container& rhs) // Copy
> constructor 2
> {
> ..........
> }
>
>
> private: ..... //
> private members defined here.
> };

--
Best regards,
Andrey Tarasevich

James Kanze

11/30/2008 9:50:00 AM

0

On Nov 29, 1:15 pm, peter koch <peter.koch.lar...@gmail.com> wrote:
> On 29 Nov., 12:16, "ravajappa.go...@gmail.com"

> <ravajappa.go...@gmail.com> wrote:
> > Hi! Can somebody tell me when does copy constructor 1 or 2
> > gets called in a template class below? And if you can
> > explain the difference between the 1 and 2 below would be
> > great?

> > template<typename T, size_t size>
> > class container {

> > public:
> >   container()   //default constructor.
> >   {
> >   }

> >   template<typename cT, size_t cs>                    // Copy
> > constructor 1
> >   container(const container<cT, cs>& rhs)
> >   {
> >       ........
> >   }

> >   container(const container& rhs)                        // Copy
> > constructor 2
> >   {
> > ..........
> >   }

> > private: .....                                                             //
> > private members defined here.
> > }

> The second constructor is the default copy-constructor and
> will be called whenever a normal copy constructor would
> normally be called.

That's not quite true. The only real effect of the second
(other than those associated with any constructor) is to
suppress the automatic generation of the copy constructor by the
compiler. In any given situation, which constructor is called
will depend on operator overload resolution, and it is quite
possible to design a class so that the template constructor is
called for copying. (Admittedly, this is a rather exotic point,
and it's not likely to affect most people's code.)

--
James Kanze (GABI Software) email:james.kanze@gmail.com
Conseils en informatique orientée objet/
Beratung in objektorientierter Datenverarbeitung
9 place Sémard, 78210 St.-Cyr-l'École, France, +33 (0)1 30 23 00 34

peter koch

11/30/2008 10:03:00 AM

0

On 30 Nov., 10:50, James Kanze <james.ka...@gmail.com> wrote:
> On Nov 29, 1:15 pm, peter koch <peter.koch.lar...@gmail.com> wrote:
>
>
>
>
>
> > On 29 Nov., 12:16, "ravajappa.go...@gmail.com"
> > <ravajappa.go...@gmail.com> wrote:
> > > Hi! Can somebody tell me when does copy constructor 1 or 2
> > > gets called in a template class below? And if you can
> > > explain the difference between the 1 and 2 below would be
> > > great?
> > > template<typename T, size_t size>
> > > class container {
> > > public:
> > >   container()   //default constructor.
> > >   {
> > >   }
> > >   template<typename cT, size_t cs>                    // Copy
> > > constructor 1
> > >   container(const container<cT, cs>& rhs)
> > >   {
> > >       ........
> > >   }
> > >   container(const container& rhs)                        // Copy
> > > constructor 2
> > >   {
> > > ..........
> > >   }
> > > private: .....                                                             //
> > > private members defined here.
> > > }
> > The second constructor is the default copy-constructor and
> > will be called whenever a normal copy constructor would
> > normally be called.
>
> That's not quite true.  The only real effect of the second
> (other than those associated with any constructor) is to
> suppress the automatic generation of the copy constructor by the
> compiler.  In any given situation, which constructor is called
> will depend on operator overload resolution, and it is quite
> possible to design a class so that the template constructor is
> called for copying.  (Admittedly, this is a rather exotic point,
> and it's not likely to affect most people's code.)
>

While I was aware of your first point, your second point is new to me.
Could you give me an example of how to write the copy-constructor in a
way that it will not be called to construct an object from an object
of the same type, using my generic templated constructor instead? I
have wanted to do so a few times but thought it was not possible and
instead ended up with two identical pieces of code.

/Peter

Dave Kelly

11/28/2011 10:19:00 PM

0


"dr.narcolepsy" <jminpa@gmail.com> wrote in message
>
> As with most of your posts, Google Groups has....

I guess you're too young to appreciate Bootys Rubber band?
Well knock me over with a feather!