Panic: the impossible happened! (3.02)

1998-06-12 Thread Mariano Suarez Alvarez
Compiling lx (the lexical analyser generator) with -O, everything goes smoothly until we get to the main file Lx.hs, on which ghc-3.02 panics and dies. The (long!) -v output is included below. If I compile without -O, everything is fine. I don't include the lx source, because I think that's

compilation of ghc3.02 fails on sparc

1998-06-12 Thread fis
Hi all, When I 'make all' the current source tree, I get the following bus error: ==fptools== make all --no-print-directory -r; in /HG/diplom/fis/src/haskell/fptools/ghc/lib/std

Re: Panic: the impossible happened! (3.02)

1998-06-12 Thread Sigbjorn Finne
Mariano Suarez Alvarez writes: Compiling lx (the lexical analyser generator) with -O, everything goes smoothly until we get to the main file Lx.hs, on which ghc-3.02 panics and dies. The (long!) -v output is included below. If I compile without -O, everything is fine. Hi, thanks - looks

Re: FW: Exceptions are too return values!

1998-06-12 Thread Fergus Henderson
On 11-Jun-1998, Amr A Sabry [EMAIL PROTECTED] wrote: There is one aspect of Java that is relevant here: A Java implementation is free to load and link classes in any order, strictly or lazily, but it MUST report exceptions as if it had loaded and resolved the classes lazily. I think

Re: Exceptions are too return values!

1998-06-12 Thread Hans Aberg
At 10:50 +1000 98/06/12, Fergus Henderson wrote: Infinities are probably best treated as a seperate issue. That is, infinities should not correspond to exceptions. If you have a type which supports infinities, then 1/0 should return infinity, not raise an exception. Conversely, if you want 1/0

Re: FW: Exceptions are too return values!

1998-06-12 Thread Alastair Reid
Fergus Henderson [EMAIL PROTECTED] points out that our exception handling scheme hits problems if you hit an infinite loop instead of an exception. Yes, this is a problem - and not a pretty one. Fixes: 1) Remove fixpoints so that infinite loops don't happen. Ok, so this isn't really an

laziness and functional middleware

1998-06-12 Thread S. Alexander Jacobson
Laziness appears to have a wierd interaction with IO. According to the docs, you should add two numbers from the user like this: main = do hSetBuffering stdout NoBuffering putStr "Enter an integer: " x1 - readNum putStr "Enter

Re: Exceptions are too return values!

1998-06-12 Thread Scott Turner
At 14:40 1998-06-10 +0100, you wrote: Here's a reasonable design for exceptions in Haskell: * handle :: (String - IO a) - IO a - IO a You probably realized more quickly than I how this can leak exceptions. What I mean is main = do quotient - handle (const (return 0)) (return (0 / 0)