The Insider News

irneb wrote:

I think that article implies comments within code blocks (e.g. inside a function). In which case I fully agree, though the "failure" isn't always just the programmer's fault, sometimes it's the language itself causing such unclear code that a comment is needed to explain what's going on (or more properly WHY).

irneb wrote:

To me those XML comments are actually documentation, not simply comments. And we all know how we feel about using a library where the documentation is non-existent or lacking detail. The fact that some tools like VS bring these documentations into the intelli-sense arena is just an extra boon.

something I dont know
     haskell was
     some time ago

something I dont know
[tab]haskell was
_____some time ago

qsort []      = []
qsort (x: xs) = qsort smaller ++ [x] ++ qsort bigger
                   where
                      smaller = [a | a <- xs, a <= x]
                      bigger = [a | a <- xs, a > x]

add a b = a + b

plusOne = add 1

// plusOne now needs to be called like: plusOne 2 (prints 3).
// The second parameter from add is "inherited".

Sander Rossel wrote:

That said, I'd still try Haskell if I were you.
Not to build any enterprise apps, but to get out of your comfort zone and do things completely different.