Hi Simon, > It relates to strictness info etc. I strongly suggest you do not try to > parse this stuff -- it was never intended for that. Why do you think > ext-core is harder? It's designed to be easier!
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. Guilherme: if you aren't 100% focused on GHC, the Yhc project has a very nice and well supported route to get out Yhc.Core - you can read about it in a The Monad Reader article (http://www-users.cs.york.ac.uk/~ndm/downloads/paper-yhc_core-30_apr_2007.pdf) or on the wiki (http://www.haskell.org/haskellwiki/Yhc/API/Core). You loose some of the advantages of GHC (working with lots of extensions, well supported), but gain a much simpler Core story. At some point I hope to hook up GHC Core to Yhc Core, and you can have 100% GHC compatibility with the nice libraries and infrastructure around Yhc.Core. Thanks Neil _______________________________________________ Cvs-ghc mailing list [email protected] http://www.haskell.org/mailman/listinfo/cvs-ghc
