Hello apfelmus, Wednesday, August 8, 2007, 11:33:41 AM, you wrote:
it's point of view of theoretical purist. i consider Haskell as language for real world apps and need to write imperative code appears independently of our wishes. in paricular, it's required to write very efficient code, to interact with existing imperative APIs, to make programs which has explicit memory control (as opposite to lazy evaluation with GC)
No and yes. As I said, it is of course desirable to be able to describe genuinely imperative behavior elegantly in Haskell, like explicit memory control or concurrently accessing a bank account.
However, most "genuinely imperative" things are often just a building block for a higher level functional model.
you say about some imaginary ideal world. i say about my own experience. i write an archiver which includes a lot of imperative code. another my project is I/O library which is imperative too. in both cases i want to make my work easier -- Best regards, Bulat mailto:Bulat.Ziganshin@gmail.com