#3858: the resolution of abbreviated commands in ghci is surprising.
-------------------------------+--------------------------------------------
  Reporter:  Saizan            |          Owner:                  
      Type:  bug               |         Status:  new             
  Priority:  normal            |      Milestone:  7.2.1           
 Component:  GHCi              |        Version:  6.12.1          
Resolution:                    |       Keywords:                  
        Os:  Unknown/Multiple  |   Architecture:  Unknown/Multiple
   Failure:  None/Unknown      |     Difficulty:                  
  Testcase:                    |      Blockedby:                  
  Blocking:                    |        Related:                  
-------------------------------+--------------------------------------------
Changes (by phercek):

  * status:  closed => new
  * resolution:  fixed =>


Comment:

 Do you need to keep it this way?

 The reason why user macros were always preferred is:[[BR]]
 * it allows users to override the default behavior of buit-in
 commands[[BR]]
 * it allows users to define priority; e.g. user may want :h to mean
 :history instead of :help; the original approach allowed this by defining
 user command :h as :history[[BR]]

 If you want ordering to be uniform everywhere what about:[[BR]]
 * user commands are always preferred[[BR]]
 * command defined later are preferred[[BR]]
 * buit-in commands have lowest precedence (but can be always accessed with
 ::)[[BR]]

 See also #3084

 If you like this approach too, I would like to get back a possibility to
 overwrite priorities and the default behavior of commands. If not, just
 close the bug without doing anything and, well, bad luck for me :)

-- 
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/3858#comment:5>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler

_______________________________________________
Glasgow-haskell-bugs mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

Reply via email to