From: Jeremiah Willcock <jewillco@osl.iu.edu>
To: gcc@gcc.gnu.org
Subject: Error message formatting feature request
Date: Wed, 01 Sep 2010 19:42:00 -0000 [thread overview]
Message-ID: <alpine.LRH.2.00.1009011537580.6563@flowerpot.osl.iu.edu> (raw)
[-- Attachment #1: Type: TEXT/PLAIN, Size: 809 bytes --]
When compiling a program such as:
template <typename T>
void foo(T, typename T::type c) {c.y();}
struct x {typedef int type;};
void f() {foo(x(), 3);}
GCC 4.5.0 (correctly) produces the error message:
foo.cpp: In function Β‘void foo(T, typename T::type) [with T = x, typename
T::type = int]Β’:
foo.cpp:4:21: instantiated from here
foo.cpp:2:34: error: request for member Β‘yΒ’ in Β‘cΒ’, which is of non-class
type Β‘x::typeΒ’
My feature request is to have the comma between "T = x" and "typename
T::type = int" replaced by a semicolon. In larger programs, the types
given in the error message often themselves contain commas, while they do
not typically contain semicolons. Thus, this change would make the error
messages easier to understand (and, in particular, to skim).
-- Jeremiah Willcock
next reply other threads:[~2010-09-01 19:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-01 19:42 Jeremiah Willcock [this message]
2010-09-01 19:46 ` Ian Lance Taylor
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=alpine.LRH.2.00.1009011537580.6563@flowerpot.osl.iu.edu \
--to=jewillco@osl.iu.edu \
--cc=gcc@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).