This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/986] g++ misses warning for & on temporary
- From: "manu at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 16 May 2007 13:03:08 -0000
- Subject: [Bug c++/986] g++ misses warning for & on temporary
- References: <bug-986-184@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #23 from manu at gcc dot gnu dot org 2007-05-16 14:03 -------
Hi Naimu, I am not speaking in the name of the GCC community but I would like
to prevent your frustration. You exposed your point clearly. People that have a
deep knowledge of C++ and g++ don't agree with you. Repeating your point again
is not doing any good.
You may go to gcc@gcc.gnu.org and expose your point to a broader audience. I
think this is going to be unsuccessful for a fundamental and a practical
reason. The fundamental reason is that the standard doesn't call this an error.
And GCC implements that C++ standard. It is the same case as with uninitialized
variables.
The practical reason is that converting a warning into an error is trivial (or
viceversa) but implementing the warning/error in the first place is not. So
people are going to say "Come back when it is implemented and we will discuss
then whether it should be a warning or an error".
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=986