Andy's example of function documentation looks fine to me. I'd also like to see HaskellDoc work at the module level too: define attributes such as an author, a version, Haskell system version, export list, imported modules, web site, repository, whatever ... In particular, I'd really like to see something that would generate an installer, capable of going from a documented Haskell program to a program that correctly installs the program, issuing any warnings / errors that are appropriate. I'd also like to see something that automates testing: note that his example contains examples that could be used to validate the module. I hope some sort of concrete proposal can be assembled at the Haskell workshop. John
- Re: Haskell Wish list: library documentation Jon . Fairbairn
- Re: Haskell Wish list: library documentation Keith Wansbrough
- Re: Haskell Wish list: library documentation Erik Meijer
- Re: Haskell Wish list: library documentation Peter Hancock
- Re: Haskell Wish list: library documentation Michael T. Richter
- Re: Haskell Wish list: library documentation Andy Gill
- Re: Haskell Wish list: library documentation Michael T. Richter
- Re: Haskell Wish list: library documentation Michael Hobbs
- Re: Haskell Wish list: library documentation Andy Gill
- Re: Haskell Wish list: library documentation Andy Gill
- Re: Haskell Wish list: library documentation John Peterson
- Re: Haskell Wish list: library documentation S. Alexander Jacobson
- Re: Haskell Wish list: library documentation trb
- RE: Haskell Wish list: library documentation Mark P Jones
- RE: Haskell Wish list: library documentation Mark P Jones
- Re: Haskell Wish list: library documentation George Russell
- Re: Haskell Wish list: library documentation Josef Sveningsson
- Re: Haskell Wish list: library documentation Martin Norb{ck
- Re: Haskell Wish list: library documentation Martin Norb{ck
- Re: Haskell Wish list: library documentation Andy Gill
- Re: Haskell Wish list: library documentation Lars Lundgren