I'm having problems with Haskell documentation that I found. Is not too clear and too simple. Where can I find any better documentation about this language?
views:
208answers:
7Personally I liked this tutorial: YAHT - Yet Another Haskell Tutorial
Subscribe to the mailing lists and use the IRC channels, Haskell has a great community don't be afraid to ask questions
I believe you may find some helpful solutions in this similar question:
http://stackoverflow.com/questions/1162360/haskell-function-cheat-sheet
There are a variety of links in the various answers there -- as the comment to your question indicates, it is hard to tell what sort of documentation you're looking for, but perhaps you'll find what it is here.
As a word of warning, if you're using GHC (as I do), the compiler errors can be hilariously incomprehensible unless if you're familiar with the underlying ideas behind Haskell. Specifically, the idea that all functions "in a way" take only 1 parameter, and how the type system works, etc. If that's your major roadblock, probably one of the tutorials kindly provided by the other answerers is your best bet for help. :)
-- Agor
Haskell itself isn't particularly clear or simple, and the learning curve can be brutal. Because of this, I'm not sure "better documentation" will help you. If you're a skilled programmer, you're probably used to using published APIs and manuals to relate what you're learning to what you already know. This doesn't work for Haskell. You have to send yourself back mentally to that first day you sat in front of your first computer. It really does feel like you're relearning everything from scratch.
Tutorials are your best bet here, particularly YAHT, the Wikibook and Real World Haskell.
Once you understand the language, you'll find that you don't rely on documentation as much as you might expect to. I've found that I can look at the source code in Haskell and truly understand what's going on with a particular function. For one thing, there's less source code to look at, and it's laid out so clearly that I can usually understand the nuts and bolts of a given function in less time than it would take me to read a set of Javadocs. But it was a test of patience before I got to this point.