On 30/04/13 10:27, William Kenyon wrote:

...

If you mean the details of bytecode compilation and the bytecode interpreter, I'm really not sure that there is. That's bad; there should be. I'm ccing Simon M in case he knows of something.

I'm just starting to write detailed documentation for the bytecode generator and interpreter as part of my Masters project,

What format would be most useful for you guys? I could do it in haddock and then include it into my project? Or just do it in plain latex and make my report publicly available?

Wiki documentation in the commentary would be the best for us. That doesn't have to be the format you write in, as long as you can translate it into Trac markup and put it in the commentary somehow. Cheers, Simon

Will

On 30 April 2013 10:02, Simon Marlow <marlowsd@gmail.com <mailto:marlowsd@gmail.com>> wrote:

From: *Simon Peyton-Jones* <simonpj@microsoft.com <mailto:simonpj@microsoft.com> <mailto:simonpj@microsoft.com <mailto:simonpj@microsoft.com>>__>

Norman

| - Is there anything published about the implementation of GHCi? | Or perhaps something on the Developers' Wiki that explains how it works?

If you mean the details of bytecode compilation and the bytecode interpreter, I'm really not sure that there is. That's bad; there should be. I'm ccing Simon M in case he knows of something.

Julian Seward wrote some notes on the way GHCi works, which are in the commentary:

http://hackage.haskell.org/__trac/ghc/wiki/Commentary/__Compiler/Backends/GH... <http://hackage.haskell.org/trac/ghc/wiki/Commentary/Compiler/Backends/GHCi>

It's not much, but there are some technical details about stacks and suchlike there. The bytecode itself is a pretty simple stack machine, I can probably answer questions if there's anything you need some help with.

Cheers, Simon

_________________________________________________ ghc-devs mailing list ghc-devs@haskell.org <mailto:ghc-devs@haskell.org> http://www.haskell.org/__mailman/listinfo/ghc-devs <http://www.haskell.org/mailman/listinfo/ghc-devs>