Skip to content

String gap failure not due to cpp

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.
Trac metadata
Trac field Value
Version None
Type Bug
TypeOfFailure OtherFailure
Priority normal
Resolution ResolvedDuplicate
Component Compiler
Test case
Differential revisions
BlockedBy
Related
Blocking
CC
Operating system
Architecture
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information