3 ms·
Nothing is said in the abstract about type system. Anyone knows if the subject is covered? Also, the book is from 1992, which should be added to the title.
by DenisM 11y ago
Nothing is said in the abstract about type system. Anyone knows if the subject is covered?
Also, the book is from 1992, which should be added to the title.
- dang 11y agoWe focus exclusively in this book on the ‘back end’ of functional-language compilers. We make no attempt to discuss how to translate programs written in a fully fledged functional language [...] or how to type-check such programs. (Added the year. Thanks.)
- nickpsecurity 11y agoI imagine this would still be useful if compilers like Haskell can produce intermediate code for what's described in the book. Not sure if they do but I have an academic paper that created a G-machine to Forth (CPU) compiler for embedded Haskell. Made me think there was a G-machine output option. Point being, plenty one can contribute to FP in terms of safety, performance, integration, and so on just knowing backends. Esp if more people do FP CPU's.
- tel 11y agoThere's a "Core" output option which is not far from STG if I remember right.
- dllthomas 11y agoGHC also has a -ddump-stg option (according to `ghc --show-options | grep stg`). I assume it does what it says on the tin...
- nickpsecurity 11y agoHere it is: https://downloads.haskell.org/~ghc/7.6.2/docs/html/users_guide/ext-core.html https://downloads.haskell.org/~ghc/7.6.2/docs/html/users_gui... The next page references dllthomas's command. Here's the language it outputs: https://ghc.haskell.org/trac/ghc/wiki/Commentary/Compiler/CoreSynType https://ghc.haskell.org/trac/ghc/wiki/Commentary/Compiler/Co... So, the trick to answer our question is if any knowledgeable readers can tell us whether what's in this guide helps on the path to understanding that language. If so, then it's a start to working with and improving it.