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: Gabriel Dos Reis <gdr at integrable-solutions dot net>
To: gcc-patches at gcc dot gnu dot org
Date: Sat, 21 Apr 2012 20:38:47 -0500
Subject: Re: [C/C++] Do not pretty-print expressions with caret diagnostics for wrong function call
References: <CAESRpQCtsxpYPM5FP0GxtgQamcXy0ht-xoqm5doyKzDLZk2Epg@mail.gmail.com> <20120421164922.GH16117@tyan-ft48-01.lab.bos.redhat.com> <CAESRpQACqoV-=b=E6jCcbC+q-N+J=APoAxJ9EuD2iY3W+UioHQ@mail.gmail.com>

I don't think the proper fix is to copy Clang.
Clang isn't the gold standard and we shouldn't
act as if it was.

When caret is not enable, the diagnostic should mention
clearly the elements in the input expressions that are problematic
without getting obtuse or elliptic -- two extremes easy to fall into.

-- Gaby

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: Jakub Jelinek
- 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]