This is the mail archive of the
mailing list for the GCC project.
Re: handling of warnings
- From: skaller <skaller at ozemail dot com dot au>
- To: Matt Austern <austern at apple dot com>
- Cc: Gabriel Dos Reis <gdr at integrable-solutions dot net>, gcc mailing list <gcc at gcc dot gnu dot org>
- Date: 14 Aug 2003 17:07:15 +1000
- Subject: Re: handling of warnings
- References: <0E8734F8-CDCE-11D7-9D31-000393B2ABA2@apple.com>
- Reply-to: skaller at ozemail dot com dot au
On Thu, 2003-08-14 at 06:38, Matt Austern wrote:
> On Wednesday, August 13, 2003, at 06:39 AM, skaller wrote:
> > Please note: I do NOT mean I can't use it because I only
> > have 3.2.2 and not the latest compiler. I can't use it because
> > the handling of unknown warning control options is BUGGED:
> > my clients could be using ANY recent variant of g++ and so I can't use
> > any new options or they won't be able to compile the code.
> Then you've got a problem with no solution. Even if you manage
> to convince people on this list that gcc should change the way
> it handles unrecognized options,
unrecognized *warning* control options
> the change won't go into the
> old compiler versions that you're concerned about.
That is true. But my main concern being here was
an 'eventual' solution.
> You'd better
> find a way to reformulate your problem so that it does have a
I'm using -w .. I don't like it much. I was hoping that
a better solution could be provided in gcc in the future
so this issue would at least eventually go away.