This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: cpp mishandles \ in filenames
- From: mike stump <mrs at windriver dot com>
- To: neil at daikokuya dot demon dot co dot uk, zack at codesourcery dot com
- Cc: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 16 Jan 2002 11:09:47 -0800 (PST)
- Subject: Re: cpp mishandles \ in filenames
> Date: Tue, 15 Jan 2002 02:11:25 -0800
> From: Zack Weinberg <zack@codesourcery.com>
> To: Neil Booth <neil@daikokuya.demon.co.uk>
> Cc: mike stump <mrs@windriver.com>, gcc-bugs@gcc.gnu.org
> Only that I asked on comp.std.c and was told point blank that
> escapes were to be interpreted.
If a windows user does #include <dir\file.h> I think they expect it to
work; it has in the past. "dir\file.h" I think should behave
likewise.
Now, if someone wants to point out that no windows compiler has ever
done this, then fine, I am waiting, but as far as I know, I've not
heard anything.
If all the windows compilers do this, then I think we should just fall
in line. What _do_ they do, what do windows programmers expect to
work?
I would rather us meet users expectations, even if the standard got it
wrong. We can always fix the standard. If someone else wants to fix
users expectations and all other windows compilers, that is fine, but
leave us out.