Title
Way objects hold allocators unclear
Status
nad
Section
[allocator.requirements]
Submitter
Angelika Langer

Created on 1998-02-23.00:00:00 last changed 171 months ago

Messages

Date: 2010-10-21.18:28:33

Rationale:

Not a defect. The LWG believes that the Standard is already clear.  See [container.requirements], paragraph 8.

Date: 1998-02-23.00:00:00

I couldn't find a statement in the standard saying whether the allocator object held by a container is held as a copy of the constructor argument or whether a pointer of reference is maintained internal. There is an according statement for compare objects and how they are maintained by the associative containers, but I couldn't find anything regarding allocators.

Did I overlook it? Is it an open issue or known defect? Or is it deliberately left unspecified?

History
Date User Action Args
2010-10-21 18:28:33adminsetmessages: + msg30
1998-02-23 00:00:00admincreate