This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/18448] g++ attempts to use copy constructor instead of operator = on instantiated object
- From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 12 Nov 2004 13:54:40 -0000
- Subject: [Bug c++/18448] g++ attempts to use copy constructor instead of operator = on instantiated object
- References: <20041112104242.18448.megath@iof.ru>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From pinskia at gcc dot gnu dot org 2004-11-12 13:54 -------
(In reply to comment #5)
> > I just says it has to be accessable
> so, if gcc dont use copy ctor - what for it complains ?!
Because this is the requirement of the C++ standard.
> and why is it error btw ?
because we could use the ctor if we wantted to in this case but we don't so the requirement of the C++
standard says it has to be accessable.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18448