This is the mail archive of the gcc-patches@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]

Re: [C/C++] Do not pretty-print expressions with caret diagnostics for wrong function call

From: Jason Merrill <jason at redhat dot com>
To: Manuel López-Ibáñez <lopezibanez at gmail dot com>
Cc: Gcc Patch List <gcc-patches at gcc dot gnu dot org>, "Joseph S. Myers" <joseph at codesourcery dot com>
Date: Tue, 24 Apr 2012 11:27:51 -0400
Subject: Re: [C/C++] Do not pretty-print expressions with caret diagnostics for wrong function call
References: <CAESRpQCtsxpYPM5FP0GxtgQamcXy0ht-xoqm5doyKzDLZk2Epg@mail.gmail.com> <4F9459F5.5070400@redhat.com> <CAESRpQDGu9_DtkZk=xG7Mk635_1WWbaNPs9OGBeFBAoC+Udncw@mail.gmail.com>

On 04/22/2012 03:49 PM, Manuel López-Ibáñez wrote:

On 22 April 2012 21:20, Jason Merrill<jason@redhat.com> wrote:
When we aren't printing the expression, please print the type instead; in a
template it might not be clear what the type of the expression we're
complaining about works out to be.
I can do that. Should I also change it in the C FE?

I think it wouldn't hurt.

Jason

References:
- [C/C++] Do not pretty-print expressions with caret diagnostics for wrong function call
  - From: Manuel López-Ibáñez
- Re: [C/C++] Do not pretty-print expressions with caret diagnostics for wrong function call
  - From: Jason Merrill
- Re: [C/C++] Do not pretty-print expressions with caret diagnostics for wrong function call
  - From: Manuel López-Ibáñez

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