Hi,
I'd like to be able to determine the percentage of allocated objects of a
particular type at specific points in a program's execution. I know that I
can use heap profiling to create a graph of memory usage broken down by type,
but is there any way to record this information at particular point
> Hello, Is calling haskell from C from haskell possible? This is what
> i tried (generated with green-card):
It ought to work. Instead of using Greencard (which only supports
Haskell->C) or the old _casm_ operation, I'd recommend using the new
foreign function interface.
http://www.cse.unsw.
let b=a in e
| -Original Message-
| From: David Sabel [mailto:[EMAIL PROTECTED]]
| Sent: 03 January 2003 15:22
| To: [EMAIL PROTECTED]
| Subject: Re: Translating seq into Core
|
| Thanks for that answer. I suggested something like that.
| Can you explain me, how the Haskell-expression
| c
Thanks for that answer. I suggested something like that.
Can you explain me, how the Haskell-expression
case a of b -> e (in Haskell, not strict, right?)
ist translated to Core?
> seq a b = case a of { DEFAULT -> b }
>
> In Core, case is always strict.
>
> | -Original Message
seq a b = case a of { DEFAULT -> b }
In Core, case is always strict.
| -Original Message-
| From: David Sabel [mailto:[EMAIL PROTECTED]]
| Sent: 03 January 2003 14:11
| To: [EMAIL PROTECTED]
| Subject: Translating seq into Core
|
| Hallo,
|
| my question ist, how the "seq" operator is t
Hello,
Is calling haskell from C from haskell possible? This is what i tried
(generated with green-card):
{-# OPTIONS -#include "Main_stub.h" #-}
module Main where
import StdDIS
foreign export ccall foo :: Int -> Int
foo i = i+1
bar :: Int -> IO Int
bar arg1 =
_casm_ ``do {int arg1;int res
Hallo,
my question ist, how the "seq" operator is translated into the
GHC-core-language?
I had suspected, the core-language has a special strictness-operator, but I
saw, that this is not the case.
David Sabel
JWGU Frankfurt
___
Glasgow-haskell-users
On Fri, Jan 03, 2003 at 03:06:48AM -0800, John Meacham wrote:
> perhaps this is related to these errors i get after my program runs for
> a while (about 2 days):
> I am guessing the no such protocol entry is because it cant open the
> /etc/protocols file due to a lack of fds. it is almost as if fil
perhaps this is related to these errors i get after my program runs for
a while (about 2 days):
I am guessing the no such protocol entry is because it cant open the
/etc/protocols file due to a lack of fds. it is almost as if file
descriptors are not being closed and leaking over time...
Connecti