#12517: Simplify runghc command line options -------------------------------------+------------------------------------- Reporter: harendra | Owner: harendra Type: bug | Status: new Priority: normal | Milestone: Component: None | Version: 8.0.1 Resolution: | Keywords: runghc Operating System: Unknown/Multiple | Architecture: | Unknown/Multiple Type of failure: None/Unknown | Test Case: Blocked By: | Blocking: Related Tickets: | Differential Rev(s): Wiki Page: | -------------------------------------+------------------------------------- Comment (by harendra): This approach looks clever at the first glance. But then: * As you noted in the end - the program name is absent in the stdin case * Usually Haskell programs (e.g. `ghc hello.hs -package text`) can specify options anywhere i.e. before or after the arguments. So designating before and after for different purposes could still be confusing because of the usual conventions being different.
your example can also be solved without --ghc-arg using: runghc -package=text-1.2.2.1 hello.hs.
I never thought about that. That's pretty nifty for current state of affairs. Yet another way. Big problem with having too many ways to do that same thing is discoverability and retention. I did not even know that ghc accepts arguments that way as well. I just looked into the man page, it is not mentioned. Could not find it in the users guide as well on a quick look in the `Using GHC` section. All of the users guide lists flags in the `-package text` convention, so that's what sticks. If I cannot easily find this and it is optional then it does not exist for me, it does not matter, its tribal knowledge. -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/12517#comment:3 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler