This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug c++/59980] New: Diagnostics relating to template-specialisations using enums.


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

            Bug ID: 59980
           Summary: Diagnostics relating to template-specialisations using
                    enums.
           Product: gcc
           Version: 4.8.1
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: gcc-bugs at hussar dot demon.co.uk

Created attachment 31978
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=31978&action=edit
Example source code producing the diagnostic.

I have a minor difference of opinion with the implementation regarding the
formatting of error messages in g++ (v4.4.7, v4.7.2 & v4.8.1, amongst others).
Examples of the error message:

test.cpp:29: error: 'fn' is not a member of 's1<(e1)1u>'
test.cpp:31: error: 'fn' is not a member of 's2<(e2)1>'

And I'd like a way to make the 's1<(e1)1u>' or 's2<(e2)1>' portion in the
message look like 's1<t2>' or 's2<e2::t4>', which is clearer (to me).

The command line used (on g++ v4.4.7 in this case) was:

g++ -Wall -Wextra -std=c++0x test.cpp


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]