This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: How would *you* use an intern?
- To: Phil Edwards <pedwards at disaster dot jaj dot com>
- Subject: Re: How would *you* use an intern?
- From: "Joseph S. Myers" <jsm28 at cam dot ac dot uk>
- Date: Thu, 31 May 2001 08:37:58 +0100 (BST)
- cc: Stan Shebs <shebs at apple dot com>, <gcc at gcc dot gnu dot org>
On Wed, 30 May 2001, Phil Edwards wrote:
> > For instance, an
> > easy thing might be to add some sort of structure to GCC's errors
> > and warnings,
>
> Gabriel Dos Reis had some rewrite of the diagnostics routines planned.
> I think he was going to break them down into categories, including
> "informational" messages (e.g., "by the way, we're using this conversion
> sequence, which you maybe weren't expecting"). You could check with him
> on this one.
>
> I'd like structure and highlighting along the lines of
>
> http://gcc.gnu.org/ml/libstdc++/2000-q2/msg00318.html
Other things to do with diagnostics: make the type-printing facilities
available to the C++ compiler also available to C. (Some comments on this
are filed in c/1027.) Make the verbosity of diagnostics configurable.
(E.g. when warning about assignment from incompatible pointer type,
minimally verbose diagnostics would do just that, and with greater
verbosity the types in question would be printed, either using typedefs or
fully broken down.)
--
Joseph S. Myers
jsm28@cam.ac.uk