This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug preprocessor/12743] [3.4 Regression] Multi-line strings not diagnosed when occurring in a macro call
- From: "jsm at polyomino dot org dot uk" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 24 Oct 2003 15:27:12 -0000
- Subject: [Bug preprocessor/12743] [3.4 Regression] Multi-line strings not diagnosed when occurring in a macro call
- References: <20031023135802.12743.gabor.greif@lucent.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=12743
------- Additional Comments From jsm at polyomino dot org dot uk 2003-10-24 15:26 -------
Subject: Re: [3.4 Regression] Multi-line strings
not diagnosed when occurring in a macro call
On Fri, 24 Oct 2003, neil at daikokuya dot co dot uk wrote:
> This is intended behaviour. It's undefined according to the
> standard, and I changed the way we do it in 3.4.
Although undefined so the standard doesn't _require_ diagnostics (for
unterminated string and character constants) there's a clear regression in
usefulness that unportable code with such unterminated constants
(_wherever_ they appear, including in skipped blocks or #error or #warning
lines or macro definitions) no longer receives diagnostics to indicate
their unportability (even with -pedantic -Wall -Wextra). AFAICT there's
also a documentedness regression (I don't recall any response to my
request <http://gcc.gnu.org/ml/gcc-patches/2003-04/msg01855.html> for
documentation of these extensions, and don't see any such documentation in
the CPP manual).