This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: wrong operator=() taken

To: "Marc Winter (HiWi)" <marcw at nick-5 dot neuro dot informatik dot uni-kassel dot de>
Subject: Re: wrong operator=() taken
From: Alexandre Oliva <oliva at dcc dot unicamp dot br>
Date: 24 Aug 1999 15:05:37 -0300
Cc: gcc-bugs at gcc dot gnu dot org
References: <Pine.A41.4.05.9908241229290.23028-100000@nick-5.neuro.informatik.uni-kassel.de>

On Aug 24, 1999, "Marc Winter (HiWi)" <marcw@nick-5.neuro.informatik.uni-kassel.de> wrote:

> 	A::operator=

> I think the output should have been:

> 	C::operator=

Nope.  An `operator=(const C&)' is implicitly generated for C<T>, and
it is preferred over `operator=(const A<T>&)' in overload resolution.
It calls B's `operator=(const B&)', also implicitly defined, and this
one calls A's `operator=(const A&)'.

-- 
Alexandre Oliva http://www.dcc.unicamp.br/~oliva IC-Unicamp, Bra[sz]il
oliva@{dcc.unicamp.br,guarana.{org,com}} aoliva@{acm.org,computer.org}
oliva@{gnu.org,kaffe.org,{egcs,sourceware}.cygnus.com,samba.org}
** I may forward mail about projects to mailing lists; please use them

References:
- wrong operator=() taken
  - From: Marc Winter (HiWi)

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]