This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/33124] C++ frontend should not warn about new a[0] in template context
- From: "gdr at cs dot tamu dot edu" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 21 Aug 2007 00:19:18 -0000
- Subject: [Bug c++/33124] C++ frontend should not warn about new a[0] in template context
- References: <bug-33124-1313@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #5 from gdr at cs dot tamu dot edu 2007-08-21 00:19 -------
Subject: Re: C++ frontend should not warn about new a[0] in template context
"ian at airs dot com" <gcc-bugzilla@gcc.gnu.org> writes:
| The problem I see is that this unconditional warning warns about code which
is
| completely safe and correct. That break -Werror builds.
I believe we agree with that.
| There is no natural way to avoid the warning in a template.
The user has no natural way to avoid that -- I agree.
However, the cure of not warning at all is too drastic.
| Given that, if we want to have this
| warning enabled even when the argument derives from a template parameter,
then
| I think that we should disable the warning by default. And given that, maybe
| we should just remove the warning.
I'm OK with that idea if that is OK with you.
-- Gaby
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33124