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: "ggreif at lucent dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 24 Oct 2003 13:41:06 -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 ggreif at lucent dot com 2003-10-24 13:41 -------
Subject: Re: [3.4 Regression] Multi-line strings
not diagnosed when occurring in a macro call
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.
>
> Neil.
I readily accept that this is forbidden by the standard,
I just wanted to criticize that the error message is
directing me to the end of the file being compiled.
I find that old code sometimes has such constructs a dozen
times, and without a line number it is _really_ hard to find
them in the code.
In fact I request that the reported line number refers to the
location of the multi-line string and tell me "multi-line string
literals are not supported any more".
The emphasis is the line number.
Thanks anyway for the prompt response,
Gabor