#10560: -f and -O options interact in non-obvious, order dependent ways -------------------------------------+------------------------------------- Reporter: bgamari | Owner: Type: bug | Status: new Priority: normal | Milestone: Component: Compiler | Version: 7.10.1 Resolution: | Keywords: Operating System: Unknown/Multiple | Architecture: Type of failure: Incorrect | Unknown/Multiple warning at compile-time | Test Case: Blocked By: | Blocking: Related Tickets: | Differential Revisions: -------------------------------------+------------------------------------- Comment (by svenpanne): It's totally irrelevant if it's easy to fix: The proposed change is completely surprising, unnatural and ad hoc. When you intend to break things, you'll better have a very good reason for doing so, and I don't think that this is the case here. It is the first time that I've heard that order-dependent flags are considered a problem, quite the opposite: Making them behave differently would confuse people and cause useless work. Later options override/modify previous options, that's how most commandline tools work. By all means, improve the documentation, but leave the flag processing as it is... -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/10560#comment:11 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler