
Hi Cafe, Is there a reason that the GHCi interpreter doesn't detect and report infinite loops in statements like this (like compiled programs do) even though no CPU time appears to be used? My (admittedly weak) searching for an answer didn't turn much up. let s | not $ null s = [] in s GHCi v7.0.4 on OSX Thanks, John

On 01.06 11:06, John Van Enk wrote:
Hi Cafe,
Is there a reason that the GHCi interpreter doesn't detect and report infinite loops in statements like this (like compiled programs do) even though no CPU time appears to be used? My (admittedly weak) searching for an answer didn't turn much up.
let s | not $ null s = [] in s
GHCi v7.0.4 on OSX
Thanks, John
Hi John, I think this is a known problem in GHCi: http://hackage.haskell.org/trac/ghc/ticket/2786 Regards, Michal

Thanks.
On Sat, Jun 2, 2012 at 12:57 PM, Michal Terepeta
On 01.06 11:06, John Van Enk wrote:
Hi Cafe,
Is there a reason that the GHCi interpreter doesn't detect and report infinite loops in statements like this (like compiled programs do) even though no CPU time appears to be used? My (admittedly weak) searching for an answer didn't turn much up.
let s | not $ null s = [] in s
GHCi v7.0.4 on OSX
Thanks, John
Hi John,
I think this is a known problem in GHCi: http://hackage.haskell.org/trac/ghc/ticket/2786
Regards, Michal
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
participants (2)
-
John Van Enk
-
Michal Terepeta