This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/16055] basic_stringbuf incorrectly handles (and ultimately ignores) allocator arguments
- From: "igodard at pacbell dot net" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 18 Jun 2004 19:32:25 -0000
- Subject: [Bug libstdc++/16055] basic_stringbuf incorrectly handles (and ultimately ignores) allocator arguments
- References: <20040618112753.16055.igodard@pacbell.net>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From igodard at pacbell dot net 2004-06-18 19:32 -------
Please look more closely. The library does indeed have an Allocator argument to the template, and the constructor does indeed take an Allocator when the object is constructed. However, when the actual buffer is built (which occurs at first use) the argument that the user has given is *not* used; instead the buffer is built using its default argument.
The Standard cannot be mandating that the class accept an allocator objectr to the constructor and then never use it!
Ivan
--
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|INVALID |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16055