On 2/19/08, Neil Mitchell <[EMAIL PROTECTED]> wrote: > The ext-core stuff is more complicated, and the support libraries that > were meant to exist around it have all bit-rotted in nasty ways. As it > currently stands, Tim's work is about the easiest route to getting > Core out of GHC, but is fairly unpolished and a little ad-hoc at the > moment. Compiling the base to get out a working Core language that can > be read back has numerous pitfalls. A nice supported GHC.Core library > would be my current number one wish for GHC.
I'd like to clarify Neil's comments here. By "Tim's work", I assume he means the work I did on extending the GHC API to support so-called "internal Core" -- if you link your program against the GHC library. Although I am glad that Neil and perhaps others have found this work useful, I have abandoned it with respect to using it for my own research, and am currently focusing on getting External Core working -- towards creating that "nice supported GHC.Core library" that Neil (and I) would like. Cheers, Tim -- Tim Chevalier * http://cs.pdx.edu/~tjc * Often in error, never in doubt "The trouble with academia is that there's a lot of 'If you'll validate my program of Kumquat Studies I won't point out the uselessness of your doctorate in Nail File Studies.'" -- Sarah Barton _______________________________________________ Cvs-ghc mailing list [email protected] http://www.haskell.org/mailman/listinfo/cvs-ghc
