[ ghc-Bugs-413158 ] String gap failure not due to cpp

[noreply@sourceforge.net]

Bugs item #413158, was updated on 2001-04-02 09:55
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=108032&aid=413158&group_id=8032

Category: Compiler
Group: 4.08.2
Status: Open
Priority: 5
Submitted By: Andrew Moran (morabbin)
Assigned to: Nobody/Anonymous (nobody)
Summary: String gap failure not due to cpp

Initial Comment:
Have you tried StringGapBug2.hs that I sent in?  With 
my setup (vanilla 4.08.2) it fails even without -cpp.
The command line I use is:

    ghc-4.08.2 -c StringGapBug2.hs

and I get the following error:

    StringGapBug2.hs:27: error in character literal

I've had a quick look at Lex.lexstringgap and there 
doesn't seem to be any problem there (I had thought 
that the second \ may have been kept in the lexeme 
when starting to lex the string again, but that 
doesn't seem to be the case).

I've attached StringGapBug2.hs again.


----------------------------------------------------------------------

>Comment By: Simon Marlow (simonmar)
Date: 2001-04-03 02:06

Message:
Logged In: YES 
user_id=48280

Yup, I tried it, and got the same error, on the line that 
begins '\h', which really *is* an error, because '\h' is 
an invalid escape sequence.  If you delete that line and 
the previous one, the test compiles fine.  

Can I close this bug?

----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=108032&aid=413158&group_id=8032