This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/18411] Warning not legitimate
- From: "manus at eiffel dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 10 Nov 2004 00:42:28 -0000
- Subject: [Bug c/18411] Warning not legitimate
- References: <20041109232340.18411.manus@eiffel.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From manus at eiffel dot com 2004-11-10 00:42 -------
Thanks for your answer. I see that following the ANSI C standard forces you to
do something. But I believe the right thing to do is:
1 - make it a compile time error (better to catch those errors at compile time
rather than at run-time, like I did)
2 - make it a warning and generates the code that gcc generated in the past and
that has been working for as long as I remember.
But definitely don't do:
- produces a warning and generate code that will crash your program at run-time.
I'm definitely in favor of 2 as it would permit the code I have to continue to
work, especially when I know that I provide all the type information to the C
compiler so that it can generate the right code.
Hopefully someone will listen or convince me otherwise
With best regards,
Manu
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18411