darcs patch: when let-shrinking a tail, be sure to op... (and 4 more)
Wed Aug 11 22:45:00 PDT 2010 John Meacham
Does that mean the bug fix for the problem with Grin generating erroneous c-code is available now? :-) anyway I think i'll try this out tonight, thanks for the progress! ---------------------------------------- To: jhc@haskell.org; john@repetae.net From: john@repetae.net Date: Thu, 26 Aug 2010 04:18:55 -0700 CC: Subject: [jhc] darcs patch: when let-shrinking a tail, be sure to op... (and 4 more) Wed Aug 11 22:45:00 PDT 2010 John Meacham * when let-shrinking a tail, be sure to optimize function bodies Thu Aug 12 03:14:52 PDT 2010 John Meacham * clean up E showing, get rid of -dhtml mode, get rid of ANSI color coding, dump jhc_core to files on error Thu Aug 12 03:24:35 PDT 2010 John Meacham * clean up warnings Thu Aug 12 03:24:58 PDT 2010 John Meacham * remove ePrettyEx Thu Aug 26 02:15:09 PDT 2010 John Meacham * show text of exception when dumping core. _______________________________________________ jhc mailing list jhc@haskell.org http://www.haskell.org/mailman/listinfo/jhc
On Thu, Aug 26, 2010 at 11:52:43AM +0000, Korcan Hussein wrote:
Does that mean the bug fix for the problem with Grin generating erroneous c-code is available now? :-) anyway I think i'll try this out tonight, thanks for the progress!
Yeah, sorry about that. I just took a look and realized I hadn't pushed out those changes. I need to set up mail on my development box so I can just darcs send from there directly. (I have a big rackspace cloud server I use for development, so my physical computers are basically dumb terminals. I call it the RAIL system (Redundant Array of Inexpensive Laptops)) :) John -- John Meacham - ⑆repetae.net⑆john⑈ - http://notanumber.net/
With the latest source version of jhc the problem I was having here (http://www.haskell.org/pipermail/jhc/2010-August/000782.html) with 'whileEvents' with lambda the erroneous c-code seems to not happen any more :) I still have the weird problem of where multiple pointers obtained from foreign functions in the same scope end up having the same address of the first defined pointer in the scope. Despite that I managed to get a basic event loop with SDL working now. I did have compile-errors when building jhc libraries from source, HUnit failed to build so I just commented that out from the makefile. I tried some other bits of code I had, one using monad transformers from transformers package I had compile-errors with a monad stack of Reader, State, IO by using 'get' function for state monads I get type unification error. I found some other problems but I'll report these all in details later soon. Probably the weekend. ----------------------------------------
Date: Thu, 26 Aug 2010 14:35:24 -0700 From: john@repetae.net To: jhc@haskell.org Subject: Re: [jhc] darcs patch: when let-shrinking a tail, be sure to op... (and 4 more)
On Thu, Aug 26, 2010 at 11:52:43AM +0000, Korcan Hussein wrote:
Does that mean the bug fix for the problem with Grin generating erroneous c-code is available now? :-) anyway I think i'll try this out tonight, thanks for the progress!
Yeah, sorry about that. I just took a look and realized I hadn't pushed out those changes. I need to set up mail on my development box so I can just darcs send from there directly. (I have a big rackspace cloud server I use for development, so my physical computers are basically dumb terminals. I call it the RAIL system (Redundant Array of Inexpensive Laptops)) :)
John
-- John Meacham - ⑆repetae.net⑆john⑈ - http://notanumber.net/ _______________________________________________ jhc mailing list jhc@haskell.org http://www.haskell.org/mailman/listinfo/jhc
On Thu, Aug 26, 2010 at 10:23:18PM +0000, Korcan Hussein wrote:
With the latest source version of jhc the problem I was having here (http://www.haskell.org/pipermail/jhc/2010-August/000782.html) with 'whileEvents' with lambda the erroneous c-code seems to not happen any more :) I still have the weird problem of where multiple pointers obtained from foreign functions in the same scope end up having the same address of the first defined pointer in the scope. Despite that I managed to get a basic event loop with SDL working now.
Hmm.. can you tell me more about this pointer issue? It sounds odd. John -- John Meacham - ⑆repetae.net⑆john⑈ - http://notanumber.net/
participants (2)
-
John Meacham -
Korcan Hussein