e64170ec   
   From: daniel.kruegler@googlemail.com   
      
   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   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   
      
   HTH & 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! ]   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)