Re: copy constructor with allocator

From:

=?ISO-8859-1?Q?Daniel_Kr=FCgler?= <daniel.kruegler@googlemail.com>

Newsgroups:

comp.lang.c++.moderated

Date:

Fri, 4 May 2012 13:02:13 -0700 (PDT)

Message-ID:

<jo010l$pq$1@dont-email.me>

On 2012-05-03 23:24, Daniel Kr?gler wrote:

Am 03.05.2012 19:55, schrieb Jeffrey Schwab:

On Thursday, May 3, 2012 4:20:05 AM UTC-4, Daniel Kr?gler wrote:

On 2012-05-03 06:25, Jeffrey Schwab wrote:

std::allocator<char> a;
std::string s1(a); // fine
std::string s2(s1, a); // NO GOOD

The line marked with "NO GOOD" should be well-formed. I suggest to
create a bug report to the corresponding library implementation.

This fails for both clang 3.0 and gcc 4.7.0. It seems strange that
both implementations have the same bug.

I'm not sure what your reply should imply, but the lack of these
constructors is a clear defect against the C++11 standard. I just
guess that this was overlooked by both implementations. FYI (I
assume you want to create a bug report): The change came in with the
working paper

http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2008/n2588.pdf

due to acceptance of the scoped allocator proposal:

http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2008/n2554.pdf

I opened a bug report for this for gcc:

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

You may want to do the same for clang.

Greetings from Bremen,

Daniel Kr?gler

--
[ See http://www.gotw.ca/resources/clcm.htm for info about ]
[ comp.lang.c++.moderated. First time posters: Do this! ]