This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: Escape sequence/parse errors

To: Zack Weinberg <zack at wolery dot cumb dot org>
Subject: Re: Escape sequence/parse errors
From: Michael Vance <briareos at lokigames dot com>
Date: Wed, 6 Sep 2000 14:22:03 -0700
Cc: gcc at gcc dot gnu dot org
References: <20000906113009.D11221@namaste.lokigames-lan.com> <20000906204551.C12278@Jeffreys.suse.de> <20000906120627.A31801@wolery.cumb.org>

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

References:
- Escape sequence/parse errors
  - From: Michael Vance
- Re: Escape sequence/parse errors
  - From: Philipp Thomas
- Re: Escape sequence/parse errors
  - From: Zack Weinberg

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]