Escape sequence/parse errors

[Michael Vance]

On Wed, Sep 06, 2000 at 08:45:51PM +0200, Philipp Thomas wrote:

> misinterpreting the path name. I'd say bison should never have used '\' in

Of course.

> the path but rather '/'. AFAIK there's no way to turn off that error but

Well, it was generated on a Win32 system, which seems entirely
reasonable to me.

> either fix the generated file or bison.

Well, it's auto-generated, and that would be rather tedious, wouldn't
it? As for the second, is there some sort of spec that mandates that
gcc needs to parse # directives as having escape sequences? Then I
could see bison being in error for generating such information.

/me looks up the yacc mailing list...

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