Opened 14 years ago

Closed 14 years ago

Last modified 45 years ago

#522 closed bug (Duplicate)

String gap failure not due to cpp

Reported by: morabbin Owned by: nobody
Priority: normal Milestone:
Component: Compiler Version: None
Keywords: Cc:
Operating System: Architecture:
Type of failure: Test Case:
Blocked By: Blocking:
Related Tickets: Differential Revisions:

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 (1)

StringGapBug2.2.hs (688 bytes) - added by morabbin 14 years ago.

Download all attachments as: .zip

Change History (5)

Changed 14 years ago by morabbin

comment:1 Changed 14 years ago by simonmar

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?

comment:2 Changed 14 years ago by simonmar

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?

comment:3 Changed 14 years ago by simonmar

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?

comment:4 Changed 14 years ago by simonmar

  • Status changed from assigned to closed
Note: See TracTickets for help on using tickets.