This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/13077] Need a way to disable warnings in code
- From: "tron dot thomas at verizon dot net" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 16 Nov 2003 21:45:47 -0000
- Subject: [Bug c++/13077] Need a way to disable warnings in code
- References: <20031116172820.13077.tron.thomas@verizon.net>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From tron dot thomas at verizon dot net 2003-11-16 21:45 -------
Subject: Re: Need a way to disable warnings in code
Using -Wno-ctor-dtor-privacy will certainly work for the case I
described. It's still not ideal as it may be difficult to apply it only
when needed for a project that is more complicated.
Development tools like Project Builder for Mac OS X using GCC as its
compiler. Project Builder does not use make files, and there is no way
to apply a certain compiler flag to a specific module. This means I
cannot modify a make file to app -Wno-ctor-dtor-privacy for particular
modules that would cause an invalid warning. I can only apply it
globally to all modules built by the project. This isn't desirable. I
would like to warning to be effective in cases where it would be valid.
Being able to disable the warning within the source code allows for the
granularity needed to disable the warning only for areas where the
warning should not apply.
bangerth at dealii dot org wrote:
>------- Additional Comments From bangerth at dealii dot org 2003-11-16 17:58 -------
>What's wrong with
> -Wno-ctor-dtor-privacy
>in this case?
>
>W.
>
>
>
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13077