This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/13864] stl_hastable.h Line 527
- From: "gdr at integrable-solutions dot net" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 26 Jan 2004 06:38:54 -0000
- Subject: [Bug libstdc++/13864] stl_hastable.h Line 527
- References: <20040126054235.13864.greg.bertin@solacesystems.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From gdr at integrable-solutions dot net 2004-01-26 06:38 -------
Subject: Re: New: stl_hastable.h Line 527
"greg dot bertin at solacesystems dot com" <gcc-bugzilla@gcc.gnu.org> writes:
| _Construct(&__n->_M_val, __obj); being called with an unitialized memory
| pointer (__n) being passed as the first parameter (i.e. it is memory allocated
| from an allocator in line 524). Memory should be default constructed first to
| ensure the class' copy constructor behaves properly:
|
| try {
| _Construct(&__n->_M_val);
| _Construct(&__n->_M_val, __obj);
| return __n;
| }
I don't understand. Why should a default construction be needed
before a copy-construction? A constructor is called only once in an
object lifetime.
-- Gaby
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13864