Ticket #522 (closed bug: Duplicate)
String gap failure not due to cpp
Description
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.
Attachments
Change History
Note: See
TracTickets for help on using
tickets.

