Hi!
2011/1/14 gutti
automata could be used. In that case all u have to do is to give the class the right properties and that "let it grow".
Such a localised intelligence approach seems an ideal OO - task. I don't know whether something functional could achieve the same.
Thanks to your question, I took another look and the old and wonderful OOHaskell paper. It is very well written and describes almost exhaustively the haskell alternatives and their shortcomings: http://homepages.cwi.nl/~ralf/OOHaskell/paper.pdf Honestly, with the information I can have, my view is that the ·"let it grow" issue in the full is only achievable by following the OOHaskell path, but you can use the other ways paying a little price. This past discussion also applies: http://www.haskell.org/pipermail/haskell-cafe/2006-January/013925.html
Sounds like a nice challenge. -- I'll chew on a small example.
Cheers Phil -- View this message in context: http://haskell.1045720.n5.nabble.com/H98-OOHaskell-getting-started-with-obje... Sent from the Haskell - Haskell-Cafe mailing list archive at Nabble.com.
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe