From: "Manuel López-Ibáñez" <lopezibanez@gmail.com>
To: Jeremiah Willcock <jewillco@osl.iu.edu>
Cc: gcc@gcc.gnu.org, Gabriel Dos Reis <gdr@cs.tamu.edu>,
Jason Merrill <jason@redhat.com>,
Mark Mitchell <mark@codesourcery.com>,
Nathan Sidwell <nathan@codesourcery.com>
Subject: Re: Error message formatting feature request [C++]
Date: Wed, 01 Sep 2010 20:12:00 -0000 [thread overview]
Message-ID: <AANLkTim-SeAmpWC3RsiZH2rXB4ObD+R3bEmGEqG6Wxut@mail.gmail.com> (raw)
2010/9/1 Jeremiah Willcock <jewillco@osl.iu.edu>:
>
> 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).
If you get a C++ or diagnostics maintainer to approve such change, I
will write a patch and test it. Maintainers are listed in the
MAINTAINERS file.
Cheers,
Manuel.
reply other threads:[~2010-09-01 20:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=AANLkTim-SeAmpWC3RsiZH2rXB4ObD+R3bEmGEqG6Wxut@mail.gmail.com \
--to=lopezibanez@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=gdr@cs.tamu.edu \
--cc=jason@redhat.com \
--cc=jewillco@osl.iu.edu \
--cc=mark@codesourcery.com \
--cc=nathan@codesourcery.com \
/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).