public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gcc-bugs at hussar dot demon.co.uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/59980] New: Diagnostics relating to template-specialisations using enums.
Date: Wed, 29 Jan 2014 12:04:00 -0000	[thread overview]
Message-ID: <bug-59980-4@http.gcc.gnu.org/bugzilla/> (raw)

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


             reply	other threads:[~2014-01-29 12:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-29 12:04 gcc-bugs at hussar dot demon.co.uk [this message]
2014-01-29 14:33 ` [Bug c++/59980] " redi at gcc dot gnu.org
2014-01-29 14:50 ` jakub at gcc dot gnu.org
2014-01-31 14:05 ` gcc-bugs at hussar dot demon.co.uk
2014-01-31 14:29 ` redi at gcc dot gnu.org
2020-04-13 11:09 ` gcc-bugs at hussar dot me.uk
2020-04-13 11:10 ` gcc-bugs at hussar dot me.uk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-59980-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).