On 10/11/2010 17:52, Mitar wrote:
Hi!
On Wed, Nov 10, 2010 at 4:16 PM, Simon Marlowmarlo...@gmail.com wrote:
The right way to fix it is like this:
Optimist. ;-)
let run = unblock doSomething `catches` [
Handler (\(_ :: MyTerminateException) - return ()),
Hi Greg,
Thanks very much for all your work on this, and Barney Stratford too. This
is great news. I'm doing a lot of numerical work with Doubles at the
moment, so progress is quite welcome!
I can try building 7.0.1-RC using a 32-bit 6.12.3, although probably not
until the weekend. I'll let
On 11/11/2010 11:17, John Lato wrote:
Hi Greg,
Thanks very much for all your work on this, and Barney Stratford too.
This is great news. I'm doing a lot of numerical work with Doubles at
the moment, so progress is quite welcome!
FYI, GHC 7.0.1 has -msse2 which makes floating-point
Hi John,
I'll take a look at trac #2965. You should be able to build the
7.0.1-rc2 tarball
simply by unpacking it and following the instructions in the README.
(In short,
configure, make then make install ought to work.)
If it doesn't build properly out of the box, I'd be interested in
Relatedly, it seems that it takes a nontrivial amount of time for
the multithreaded RTS to realize that a thread has emitted a
signal. I wonder if there's a more direct way an FFI call can say
when I get back to Haskell, immediately start propagating an exception.
Edward
Hello,
the following program should wait 3 seconds for user input before. If
now user input occurs within that time, it just prints -1.
{-# LANGUAGE ForeignFunctionInterface #-}
module Main where
import Foreign
import Foreign.C.String
import Foreign.C.Types
import
Quoth Simon Hengel simon.hen...@wiktory.org,
...
This works just fine if I do not use the threaded RTS, say:
ghc --make -lcurses Main.hs
However, with
ghc --make -threaded -lcurses Main.hs
I bet, if you switch off the barrage of thread scheduling SIGALRMs,
+RTS -V0 -RTS , it will
ghc --make -threaded -lcurses Main.hs
I bet, if you switch off the barrage of thread scheduling SIGALRMs,
+RTS -V0 -RTS , it will work like it's supposed to.
That helped, thanks!
Cheers,
Simon
___
Glasgow-haskell-users mailing list
Excerpts from Donn Cave's message of Thu Nov 11 17:07:20 -0500 2010:
ghc: 6.12.1
linux: 2.6.32
ncurses: 5.7
Someone probably should. It's tempting to conclude that the bug
is in ncurses, and perhaps it is, and maybe there's nothing to be
done about it anyway, but a language
On Thu, Nov 11, 2010 at 2:32 PM, Edward Z. Yang ezy...@mit.edu wrote:
I was under the impression we fixed this:
http://hackage.haskell.org/trac/ghc/ticket/850
That is, we should be using SIGVTALRM, not SIGALRM, these days, except
under certain conditions when your operating system
Quoth Simon Hengel simon.hen...@wiktory.org,
ghc --make -threaded -lcurses Main.hs
I bet, if you switch off the barrage of thread scheduling SIGALRMs,
+RTS -V0 -RTS , it will work like it's supposed to.
That helped, thanks!
Great, but, beware - I am not fully informed on what it
Hi!
On Wed, Nov 10, 2010 at 4:48 PM, Simon Marlow marlo...@gmail.com wrote:
You can use maskUninterruptible in GHC 7, but that is not generally
recommended,
Maybe there should be some function like maskUninterruptibleExceptUser
which would mask everything except UserInterrupt exception. Or
12 matches
Mail list logo
