[Haskell-cafe] Arrows: definition of pure & arr
jgbailey at gmail.com
Tue Feb 19 14:13:44 EST 2008
On Feb 19, 2008 8:04 AM, Peter Verswyvelen <bf3 at telenet.be> wrote:
> Actually, if you look at the way OO programmers design code, they usually choose long descriptive names, like "FindElementByName". Most Haskell people seem more math oriented and use very short names, like "fst" and "snd" (which are a bit better than the old "car" and "cdr"). Now in the end, once you get used to a name, it doesn't matter does it?
I also think this comes from better IDE support. When I'm coding in
C#, I choose longer method, class, and property names because Visual
Studio frees me from having to type the entire thing - Intellisense
does most of the work. When I am coding in PHP or Haskell, with poor
IDE support, I tend for shorter.
I think a secondary influence comes from the need to typeset code in
journals and books. Even if you don't actually publish your code, the
people who have written the existing papers and tutorials did, and
that influence the style you learn.
More information about the Haskell-Cafe