Opened 8 years ago

Closed 15 months ago

#733 closed bug (duplicate)

Problem compiling .lhs files with lines that begin with #

Reported by: guest Owned by:
Priority: low Milestone:
Component: Compiler Version: 6.4.1
Keywords: Cc:
Operating System: Unknown/Multiple Architecture: Unknown/Multiple
Type of failure: None/Unknown Difficulty: Unknown
Test Case: Blocked By:
Blocking: Related Tickets:

Description

Lines starting with # inside a .lhs make ghc yield "lexical error".

Change History (5)

comment:1 Changed 8 years ago by simonmar

  • Priority changed from normal to low
  • severity changed from normal to minor

This is true, the idea is to leave CPP directives intact. When not using CPP it would make sense to ignore these '#' lines. Unfortunately, at the time we are unlitting, we don't know whether we will be running CPP or not (the -cpp flag might be in the OPTIONS_GHC pragma, which can't be parsed until unlit is finished). Perhaps we could do a two-pass unlit or something, but that sounds like too much effort.

I doubt we'll fix this, but thanks for the report anyway.

comment:2 Changed 7 years ago by igloo

  • Milestone set to _|_

comment:3 Changed 6 years ago by simonmar

  • Architecture changed from Unknown to Unknown/Multiple

comment:4 Changed 6 years ago by simonmar

  • Operating System changed from Unknown to Unknown/Multiple

comment:5 Changed 15 months ago by morabbin

  • Resolution set to duplicate
  • Status changed from new to closed
  • Type of failure set to None/Unknown

Closing; superseded by #4836.

Note: See TracTickets for help on using tickets.