From: Ian Lance Taylor <iant@google.com>
To: Jeremiah Willcock <jewillco@osl.iu.edu>
Cc: gcc@gcc.gnu.org
Subject: Re: Error message formatting feature request
Date: Wed, 01 Sep 2010 19:46:00 -0000 [thread overview]
Message-ID: <mcrwrr58cxx.fsf@google.com> (raw)
In-Reply-To: <alpine.LRH.2.00.1009011537580.6563@flowerpot.osl.iu.edu> (Jeremiah Willcock's message of "Wed, 1 Sep 2010 15:41:58 -0400 (EDT)")
Jeremiah Willcock <jewillco@osl.iu.edu> writes:
> 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).
Thanks for the suggestion. Please open a feature request at
http://gcc.gnu.org/bugzilla/ for this. Otherwise I'm afraid this
suggestion will just be lost in the noise.
Ian
prev parent reply other threads:[~2010-09-01 19:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-01 19:42 Jeremiah Willcock
2010-09-01 19:46 ` Ian Lance Taylor [this message]
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=mcrwrr58cxx.fsf@google.com \
--to=iant@google.com \
--cc=gcc@gcc.gnu.org \
--cc=jewillco@osl.iu.edu \
/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).