tag:blogger.com,1999:blog-11295132.post114727930110263308..comments2007-02-08T19:54:45.997-08:00sigfpehttp://www.blogger.com/profile/08096190433222340957noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-11295132.post-1147364107100924112006-05-11T09:15:07.100-07:002006-05-11T09:15:07.100-07:00Kim-ee,<BR/><BR/>My code is an amalgamation of various ideas I picked up by skimming a bunch of documents like that tutorial. I find that it's better to try to implement something first and then read the papers - that way you have a better appreciation for what the problems are. In fact, many statements I'd read about lazy functional compiler writing used to make no sense to me at all, but now make perfect sense. So I'll probably read that tutorial properly some time soon.sigfpehttp://www.blogger.com/profile/08096190433222340957noreply@blogger.comtag:blogger.com,1999:blog-11295132.post-1147321829237138682006-05-10T21:30:29.236-07:002006-05-10T21:30:29.236-07:00I can relate to some of your experiences developing a compiler. One of the better kept secrets for learning Haskell is Peyton-Jones and Lester's <A HREF="http://research.microsoft.com/~simonpj/Papers/pj-lester-book/" REL="nofollow"> Implementing functional languages: a tutorial</A>, which guides you through several ways of executing Haskell, including the G-machine at the heart of GHC.<BR/><BR/>Best of luck on the embedded project. I'd really be keen to know how it turns out.Kim-Ee Yeohhttp://www.blogger.com/profile/03063816445379881605noreply@blogger.com