[Bug libstdc++/14245] problem with user-defined allocators in std::basic_string

[pcarlini at suse dot de]

------- Additional Comments From pcarlini at suse dot de  2004-02-25 09:48 -------
Hi. Honestly, I'm finding your report a little misleading: there is nothing wrong
with using the default constructor: its availability is among the requirements
for allocators (20.1.5, Table 32), and you find it everywhere in basic_string.

Anyway... probably I get your point: you mean that, at string construction time,
we should use _M_refcopy (not _M_clone) irrespective of the allocator used for
__str, in other terms, _Alloc() is not special.

Do you agree with my exegesis? ;)

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|unassigned at gcc dot gnu   |pcarlini at suse dot de
                   |dot org                     |
             Status|UNCONFIRMED                 |ASSIGNED
     Ever Confirmed|                            |1
   Last reconfirmed|0000-00-00 00:00:00         |2004-02-25 09:48:57
               date|                            |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14245