Also, get a load of this Walter Bright guy. "The easiest way to show the error is consider the code being ported to a
typical 64 bit C compiler. int's are still 32 bits, yet the array can be larger than 32 bits." Yes yes, and I would certainly iterate over an array's indices with a simple for loop even if said array would become larger than can be indexed with 32-bit signed integers. NOT! Fucking hell. 31 bits' worth of indexes in an array of the smallest C datatype, "char", would be two fucking gigabytes of continuous memory! Whomever has reason to iterate over that much data either needs himself a computation cluster, a brain, or a life.
>>38
C and Haskell. The first is the traditional tool from a more civilized era (lulz) and the second provides the completely wonderful experience of programming without having to think about execution order or when one can replace a value in a variable. That last bit is important, because mutable variables are just as much manual memory management as malloc and free.
Also, Haskell got me into formal specification. Take a look at the Z notation for shits and giggles and getting your mind pried open like a pretzel.
Ok, I'll admit to using a spot of Perl in text-processing and database access things. And shellscript for automating rsync and backup tasks. I've never had a hankering to do anything in Python however.