|
![](/i/fill.gif) |
Darren New wrote:
> Orchid XP v8 wrote:
>> If I ever did write a book on Haskell, would this make a good chapter?
>
> Indeed! Actually, it should be near the front, I think. (But I'm a
> computer language nerd, so maybe not.)
This was my thinking also. A chapter with no code, just concepts.
I've tried writing Haskell tutorials before, and I always get stuck
here, because you need ADTs to explain pattern matching, but you need
pattern matching to explain ADTs. I think explaining how it all works
before trying to write code is probably the way forward. Indeed, I'm
thinking this might significantly simplify other aspects too - teach 'em
how it all works before you get into the details of syntax and so forth.
> I'll second that you should write a Haskell book. I bet I know someone
> who could tell you the right person to point you at at O'Reilly if you
> wanted to see if it could go commercial, too. I wouldn't give the
> rights away *too* fast.
Heh. O'Reilly just published one:
http://book.realworldhaskell.org/
It's written by three leading Haskell experts too.
Nice idea though. ;-)
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
![](/i/fill.gif) |