[Haskell] Re: package mounting

2006-10-29 Thread Frederik Eaton
On Sun, Oct 29, 2006 at 10:03:32PM -0400, Samuel Bronson wrote: > On 10/25/06, Frederik Eaton <[EMAIL PROTECTED]> wrote: > > >http://hackage.haskell.org/trac/ghc/wiki/PackageMounting > > It looks nice, but don't you think the -package-base flag ought to > take both the package name *and* the moun

Re: [Haskell] wxHaskell for GHC 6.6 and wxWidget 2.6.2

2006-10-29 Thread Eric Y. Kow
On Sun, Oct 29, 2006 at 22:04:44 -0800, Sukit Tretriluxana wrote: > I saw someone posting a comment (http://sequence.complete.org/node/214) > about the build of wxHaskell for GHC 6.6 and wxWidget 2.6.2 but it's not > currently hosted anywhere yet. Does anyone know where can I get the Windows > bina

[Haskell] wxHaskell for GHC 6.6 and wxWidget 2.6.2

2006-10-29 Thread Sukit Tretriluxana
Hi,I saw someone posting a comment (http://sequence.complete.org/node/214) about the build of wxHaskell for GHC 6.6 and wxWidget 2.6.2 but it's not currently hosted anywhere yet. Does anyone know where can I get the Windows binary build of it for the time being? Thanks,Ed __

[Haskell] [Announce] Yhc Bytecode library 0.3

2006-10-29 Thread Robert Dockins
[Please direct disccusion to the yhc list] Fellow Haskellers, I am pleased to announce the release of the Yhc Bytecode library, version 0.3. The major differences from version 0.2 are: * Updated to work with the current Yhc development branch as of 2006-10-13 * API modified to fully handl

[Haskell] Re: Infinite, open, statically constrained HLists

2006-10-29 Thread Chung-chieh Shan
[EMAIL PROTECTED] wrote in article <[EMAIL PROTECTED]> in gmane.comp.lang.haskell.general: > We show a presentation of heterogeneous sequences that admits infinite > sequences and permits post-hoc addition of new elements, even to an > already infinite sequence. We can also assert static constrain

[Haskell] How to find out who is leaking memory?

2006-10-29 Thread [EMAIL PROTECTED]
My program is leaking memory. It is fairly complex and long running on the test that leaks. On that particular test it exits abnormally telling me that heap is overflown. Is there a way to find out what part is leaking memory without refactoring? __