This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: feature request
- From: "Sam Lauber" <sam124 at operamail dot com>
- To: "Ian Lance Taylor" <ian at wasabisystems dot com>, gcc at gcc dot gnu dot org
- Date: Wed, 17 Nov 2004 04:02:59 +0100
- Subject: Re: feature request
Wrapper program? That wouldn't exactly be a simple programming job because I would probably have to duplicate all the source-file reading (or at least parsing) code from GCC. I would also have to make the warnings in the exact same format that GCC uses. Which just the line wrap seems hard. If your idea is for that, count me out. Whenever I try to program anything more than 10 lines of code, GCC gives me 1000 errors for everything, and if I put -Wall, it gives me 10000 warnings.
Samuel Lauber
----- Original Message -----
From: "Ian Lance Taylor" <ian@wasabisystems.com>
To: "Luca Benini" <lbenini@csr.unibo.it>
Subject: Re: feature request
Date: 16 Nov 2004 13:27:03 -0500
>
> Luca Benini <lbenini@csr.unibo.it> writes:
>
> > Joe Buck wrote:
> > > That would be really ugly for those of us that use gcc from an IDE
> >
> > But a little flag? something like -Wiwanteyecandyoutput ?
> > During long compiling session in console (make) this feature can be
> > useful or not?
>
> How about first writing and contributing a little wrapper program that
> you pipe gcc stderr through? Then maybe we could add a gcc option
> which automatically invoked that program on stderr.
>
> Ian
>
--
_____________________________________________________________
Web-based SMS services available at http://www.operamail.com.
From your mailbox to local or overseas cell phones.
Powered by Outblaze