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:51:13 -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:51 -------
Subject: Re: Need a way to disable warnings in code
Well. the case I present was obviously a contrived example for
demonstration purposes. The HeapObject class doesn't do anything except
allow the use to delete objects allocated on the heap, and that's not
useful for much of anything.
The real problem I'm having is that 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.
I don't really consider what I logged into the database as a bug per
se. It is more of a feature request that I feel will improve the
quality of the GCC compiler.
pinskia at gcc dot gnu dot org wrote:
>------- Additional Comments From pinskia at gcc dot gnu dot org 2003-11-16 18:23 -------
>This is good improvement.
>But in this case since it is already a flag, just use that flag.
>I thought I saw a dup of this bug before but I cannot find it.
>
>
>
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13077