Escape sequence/parse errors

[Michael Vance]

On Wed, Sep 06, 2000 at 12:06:27PM -0700, Zack Weinberg wrote:

> This is a dark corner of the standard.  I don't like it much, but:
> 
> #include "dir\name.h"	/* undefined behavior */
> #line 1 "dir\name.h"	/* string contains a newline */

Ah, okay, thanks. I've forwaded this on to the people who generate
these files in an attempt to get them to correct it.

> I believe the error will become a warning with -fpermissive.

Whee. This works great, thanks.

m.

-- 
Programmer             "Ha ha." "Ha ha." "What are you laughing at?"
Loki Software                      "Just the horror of being alive."
http://lokigames.com/~briareos/                   - Tony Millionaire