This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug preprocessor/12607] preprocessor fails to diagnose an undefined ## result
- From: "sebor at roguewave dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 14 Oct 2003 20:57:30 -0000
- Subject: [Bug preprocessor/12607] preprocessor fails to diagnose an undefined ## result
- References: <20031013234821.12607.sebor@roguewave.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12607
------- Additional Comments From sebor at roguewave dot com 2003-10-14 20:57 -------
Sorry, I should have perhaps been more specific. Let me reiterate my suggestion:
replace the hard error in case #1 (undefined behavior) with a warning when -Wall
is on the command line, silently accept it when it isn't, and have -Werror turn
the warning into a hard error.
The value in this feature (i.e., permissive behavior) is in making it easier to
port to gcc programs that rely on this sort of undefined behavior from compilers
that accept the construct.
Martin