RE: ghc-cvs-snapshot with wxHaskell

Thanks this looks like a bug that was introduced recently. Now fixed. Cheers, Simon On 08 February 2005 11:43, Patrick Scheibe wrote: Hi, Could you tell us what command line was supposed to generate the Map.d.in or Map.d file? It may be a bug, there were a few changes in the

RE: GHC 6.4 release candidates available

On 14 February 2005 17:23, Ross Paterson wrote: If a program calls exitWith, runghc produces an extra line of output: *** Exception: exit: ExitSuccess or *** Exception: exit: ExitFailure 3 and then exits with status 0. It should do what a ghc-compiled program does: silently exit with the

Re: ghc-cvs-snapshot with wxHaskell

Hi Simon, thank you for having a look at this. I will test it and I hope can compile wxHaskell tonight. Where is the fixed version of the ghc? Is it one of the stable night releases or should I make a update of the developer cvs tree of ghc?? Cheers Patrick On Tuesday 15 February 2005

Increasing heap size

Hello! I have problems when building a large haskell system (haskell-jvm bridge). The compiler complains (see below) that the heap size is too small and limited to about 268 MB. error-messages $ make C:/Programme/haskell-jvm-bridge-0.3-RC1/bin/MakeJVMModule HelloWorld_JVM HelloWorld_JVM.list

writing to stdout in an windows app without a console

This might be a bug report but it's definitely a question on what the behaviour should be: On windows if you link using --subsystem windows then your program starts without popping up a console. This is good for GUI apps (and we would like to make it the default when using gtk2hs on win32 by

Re: writing to stdout in an windows app without a console

Hi Duncan With ghc-6.4 the output from Debug.Trace.trace will be redirected to the debug console when the application is compiled with --subsystem windows. You can see the trace messages with any Windows debuger. The error messages from any uncaught exception will be displayed in message box.