Opened 8 years ago

Closed 8 years ago

#1328 closed bug (fixed)

ghci accepts ":set -fno-glasgow-exts", but not ":unset -fglasgow-exts"

Reported by: cdsmith@… Owned by:
Priority: low Milestone:
Component: GHCi Version: 6.6
Keywords: Cc:
Operating System: Linux Architecture: x86
Type of failure: Test Case:
Blocked By: Blocking:
Related Tickets: Differential Revisions:

Description

Using "gchi -fglasgow-exts", I want to turn off glasgow extensions. First I try:

Prelude> :unset -fglasgow-exts can't unset GHC command-line flags

But then:

Prelude> :set -fno-glasgow-exts Prelude> :t 5 5 :: (Num t) => t

So GHCi is capable of turning off glasgow extensions, but is apparently really picky about what command is used to do it.

sorear suggested I file this as a bug.

Change History (2)

comment:1 Changed 8 years ago by guest

That should have been:

Prelude> :unset -fglasgow-exts
can't unset GHC command-line flags 

and

Prelude> :set -fno-glasgow-exts
Prelude> :t 5
5 :: (Num t) => t 

comment:2 Changed 8 years ago by simonmar

  • Resolution set to fixed
  • Status changed from new to closed

Fixed (well, I was in the area).

Note: See TracTickets for help on using tickets.