This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: cpp mishandles \ in filenames
On Mon, Jan 14, 2002 at 10:22:55PM +0000, Neil Booth wrote:
>
> > which is wrong, if we believe the standard requires escape sequence
> > interpretation in #line, and I don't believe Mike's patch addressed
> > this. (Mind, 2.95 does the same thing.)
>
> But what makes you think escape interpretation should be done (i.e.
> the stage 5 thing). Directive processing is earlier; so we've already
> decided what the new file name is.
Only that I asked on comp.std.c and was told point blank that escapes
were to be interpreted. See <I0J8sxlaKtP8EwiY@romana.davros.org> and
my response to same.
I don't think it makes a hell of a lot of sense for escapes to be
interpreted in #line, although I _can_ make a case depending on the
premise that #line will usually appear in machine-generated code.
zw