#3217: Make GHCi have separate flags for interactive Haskell expressions
---------------------------------+------------------------------------------
    Reporter:  simonpj           |        Owner:                  
        Type:  feature request   |       Status:  new             
    Priority:  normal            |    Milestone:  6.12 branch     
   Component:  Compiler          |      Version:  6.10.2          
    Severity:  normal            |   Resolution:                  
    Keywords:                    |   Difficulty:  Unknown         
    Testcase:                    |           Os:  Unknown/Multiple
Architecture:  Unknown/Multiple  |  
---------------------------------+------------------------------------------
Comment (by simonpj):

 The trouble is that there already '''is''' another layer of settings for
 interactive expressions, namely the baked-in ones concerning extended
 defaults.  The proposal here is to make that explicit, and controllable,
 rather than hidden and baked in.  The hidden, baked-in version is
 vulnerable to feature request for new baking-in, such as #3202.  If it was
 controllable, people could do that in their `.ghci` file.

 And if you want identical flags for both, then in your `.ghci` you can set
 the interactive flags to exactly match the batch flags.

 So I think its arguable that this ticket would make things simpler.  The
 other simplicity approach would to insist that the interactive and batch
 flags were identical -- but that'd mean no extended defaults which people
 would hate.

 Simon

-- 
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/3217#comment:2>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
_______________________________________________
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

Reply via email to