Re: runghc -fdefer-type-errors

2013-03-12 Thread Gabriel Dos Reis
On Mon, Mar 11, 2013 at 9:33 PM, Isaac Dupree m...@isaac.cedarswampstudios.org wrote: On 03/11/2013 07:04 PM, Simon Peyton-Jones wrote: Aha. It is indeed true that ghc -fdefer-type-errors -w does not suppress the warnings that arise from the type errors; indeed there is no current way to

runghc -fdefer-type-errors

2013-03-11 Thread 山本和彦
Hello, Doesn't runghc support the -fdefer-type-errors option? Consider this code: module Main where main :: IO () main = do -- putStrLn は文字列を取る putStrLn Hello, world! putStrLn 1 -- 型エラー If I use runghc with -fdefer-type-errors, Hello, world! is not

Re: runghc -fdefer-type-errors

2013-03-11 Thread Richard Eisenberg
When I ran this code (ghc 7.6.1), I did get the Hello, world! printout. That line was sandwiched between the compile-time warning from the type error and the run-time exception from the type error, but the output was there: 09:24:28 ~/temp runghc Scratch.hs Scratch.hs:5:12: Warning: No

Re: runghc -fdefer-type-errors

2013-03-11 Thread 山本和彦
Hi, When I ran this code (ghc 7.6.1), I did get the Hello, world! printout. That line was sandwiched between the compile-time warning from the type error and the run-time exception from the type error, but the output was there: Thank you for letting me know this. I'm also using GHC 7.6.1. I

RE: runghc -fdefer-type-errors

2013-03-11 Thread Edward Z. Yang
Excerpts from Simon Peyton-Jones's message of Mon Mar 11 16:04:31 -0700 2013: Aha. It is indeed true that ghc -fdefer-type-errors -w does not suppress the warnings that arise from the type errors; indeed there is no current way to do so. How to do that? To be kosher there should

Re: runghc -fdefer-type-errors

2013-03-11 Thread 山本和彦
should try to find why the incorrect behavior happens in my environment. I noticed that -- is necessary. runghc -- -fdefer-type-errors Main.hs --Kazu ___ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http

Re: runghc -fdefer-type-errors

2013-03-11 Thread Isaac Dupree
On 03/11/2013 07:04 PM, Simon Peyton-Jones wrote: Aha. It is indeed true that ghc -fdefer-type-errors -w does not suppress the warnings that arise from the type errors; indeed there is no current way to do so. How to do that? To be kosher there should really be a flag to switch off