the important thing when programming in Haskell is to be sure to do nothing

Submitted by metaperl on Sat, 03/19/2005 - 2:00pm.

Spend your time defining and composing. If you are trying to get something done in 2 lines, then you are trying too hard and have not separated out the task fully.

It's hard for imperative-trained programmers to grasp this, but it is vitally important.

Submitted by shapr on Wed, 03/23/2005 - 8:39am.

I don't understand, can you explain this is more detail?
Can you give an example of defining and composing?

Submitted by metaperl on Mon, 03/28/2005 - 6:26am.

my ideas about implementing those algorithms involved lots of state. So when I looked at how definitional their solutions were, I realized what I wrote... I was actually looking at the heap implementation when it hit me

I cant be more specific than this because I never wrote the imperative algorithm.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.