On 15 February 2005 20:12, Dmitri Pissarenko wrote:
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
On Wed, 2005-02-16 at 09:18 +0200, Krasimir Angelov wrote:
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
Hi,
I don't know much about the internals of GHC, but I like look around once in a
while to learn a few things. I was wondering about the definition of take,
which is, for Ints:
-
takeUInt :: Int# - [b] - [b]
takeUInt n xs
|
On Wed, 16 Feb 2005 12:01:06 +, Duncan Coutts
[EMAIL PROTECTED] wrote:
What's your opinion of making writing to stdout fail without raising an
exception when the application is compiled with --subsystem
windows?
I think the current behaviour is the right one. After all we don't
have valid
On Wed, 2005-02-16 at 14:31 +0200, Krasimir Angelov wrote:
On Wed, 16 Feb 2005 12:01:06 +, Duncan Coutts
[EMAIL PROTECTED] wrote:
What's your opinion of making writing to stdout fail without raising an
exception when the application is compiled with --subsystem
windows?
I think the
On 16 February 2005 14:06, Duncan Coutts wrote:
On Wed, 2005-02-16 at 14:31 +0200, Krasimir Angelov wrote:
On Wed, 16 Feb 2005 12:01:06 +, Duncan Coutts
[EMAIL PROTECTED] wrote:
What's your opinion of making writing to stdout fail without
raising an exception when the application is
On Wed, 2005-02-16 at 14:49 +, Simon Marlow wrote:
On 16 February 2005 14:06, Duncan Coutts wrote:
On Wed, 2005-02-16 at 14:31 +0200, Krasimir Angelov wrote:
On Wed, 16 Feb 2005 12:01:06 +, Duncan Coutts
[EMAIL PROTECTED] wrote:
What's your opinion of making writing to stdout
On Thu, Feb 10, 2005 at 01:11:48PM -, Simon Marlow wrote:
We are finally at the release candidate stage for GHC 6.4. Snapshots
with versions 6.4.20050209 and later should be considered release
candidates for 6.4.
Source and Linux binary distributions are avaiable here:
In 6.4 the duplicate import warning seems to be triggered overzealously, even
when one import is qualified and the other isn't.
import qualified Data.Map
import Data.Map(Map)
foo :: Map Int Int
foo = Data.Map.empty
main = do
print foo
produces:
