Our very own web page has a C++ FAQ about requires that a copy constructor be
visible when initializing a const reference:
    http://gcc.gnu.org/bugs/#cxx_rvalbind

However, current versions of gcc do not give an error for that code, even when
using -pedantic -std=c++98.  The last version of gcc to give the error was gcc
4.2.  This seems ironic considering that we say "most popular compilers do not
correctly implement this rule."

I think we should give that error when -pedantic.


-- 
           Summary: g++ no longer warns about private copy constructors
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: ian at airs dot com


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

Reply via email to