Try upgrading GHC.

Thanks, I'll try that. Would it be too much to ask that Haddock be distributed with GHC? Reasons for: - GHC library docs are produced with Haddock - GHC library docs already include Haddock interface files - would ensure version of Haddock matches that used to produce interface files - would save lazy developers like myself from downloading and compiling. Think of it as one less barrier to overcome; a small step closer to more widespread adoption. Reasons against: - would favour one documentation tool over others - would add an unnecessary item to GHC build/packaging procedure (is this much of an overhead?) Mind you, if you include Haddock, why stop there? Why not include other developers tools, like (say) Hmake, Happy, Hat, ...? Alistair.

-----Original Message----- From: Simon Marlow [mailto:simonmar@microsoft.com] Sent: 13 April 2004 10:59 To: Bayley, Alistair Cc: haskell-cafe@haskell.org Subject: RE: [Haskell-cafe] Building Haddock on Windows

Yes, I suspect you have a mismatch between the version of Haddock on your system and the version of Haddock used to produce the interfaces. Try upgrading GHC.

Cheers, Simon

...

-----Original Message----- From: Bayley, Alistair [mailto:Alistair_Bayley@ldn.invesco.com] Sent: 05 April 2004 16:19 To: Simon Marlow Cc: haskell-cafe@haskell.org Subject: RE: [Haskell-cafe] Building Haddock on Windows

Trying to invoke Haddock with --read-interface=c:\ghc\ghc-6.0\doc\html\base\base.haddock

Initially I get a stack overflow, so I added: +RTS -K2M -RTS ...

and now I get: Fail: end of file Action: Data.Binary.getWord8

Is the --read-interface option specified correctly? This is where my GHC installation is, and the base.haddock file exists in there. I assume this is the interface file.

Is this a compatibility problem? i.e. haddock file distributed with GHC 6.0 too old for Haddock 0.6?

----------------------------------------- ***************************************************************** Confidentiality Note: The information contained in this message, and any attachments, may contain confidential and/or privileged material. It is intended solely for the person(s) or entity to which it is addressed. Any review, retransmission, dissemination, or taking of any action in reliance upon this information by persons or entities other than the intended recipient(s) is prohibited. If you received this in error, please contact the sender and delete the material from any computer. *****************************************************************