On Friday, May 21, 2010 11:45:18 am John Lato wrote: > On Fri, May 21, 2010 at 4:56 AM, Renick Bell <[email protected]> wrote: > >> I found hp2any-manager extremely useful. > > > > Thank you for your advice. You put me on the right path. I had been > > running my code and interacting with it in ghci, which is where I > > experienced the lateness. To use hp2any, I prepared a compiled version > > and ran it, and not only was it using almost no memory (as I had > > believed), the lateness disappeared. The problem, it appears, is using > > ghci. > > > > From that, I found that doing > > > > :set -fobject-code > > > > in ghci improves the timing considerably, though it is still not perfect. > > > > Now I need to find out if it can be made any better from within ghci. > > You could try compiling the time-critical stuff with ghc -O2, then > just load the object files with ghci. That might give better results. >
IIRC, you can configure ghci not to run the code interpreted but to compile it first. (I don't know, if ghci can do that, but at least the GHC-API exposes this option, I think.) That might be interesting for people doing audio life coding in general. (And it's pretty cool, when you think about it, using a command line interpreter to run native machine code.) Cheers, Sönke _______________________________________________ haskell-art mailing list [email protected] http://lists.lurk.org/mailman/listinfo/haskell-art
