This is the mail archive of the
mailing list for the GCC project.
Re: How would *you* use an intern?
- To: "Joseph S. Myers" <jsm28 at cam dot ac dot uk>
- Subject: Re: How would *you* use an intern?
- From: Gabriel Dos Reis <gdr at codesourcery dot com>
- Date: 31 May 2001 11:00:54 +0200
- Cc: Phil Edwards <pedwards at disaster dot jaj dot com>, Stan Shebs <shebs at apple dot com>, <gcc at gcc dot gnu dot org>
- Organization: CodeSourcery, LLC
- References: <Pine.LNX.firstname.lastname@example.org>
"Joseph S. Myers" <email@example.com> writes:
| 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.
I'm definitely with you on this. Zack already asked me to publish my
intentions. I'll do shortly (I have to find an uncommited patch I
made one month ago and some notes).
CodeSourcery, LLC http://www.codesourcery.com