Yes, folks can write unmaintainable code that is hugely special-case driven, containing many large if-combs, with lots of one-offs, fudge factors, etc, and there are cases where you see code like "c&=(int)m+n+y>>3&0xFC%4". But let's not call that hacking. Let's call that "bad code". Let's call this "cluelessness" or "junior high school programming".

You get a point on that one, when i see c &= (int) m+n+y >> 3 & 0xFC % 4, i'd call that "idioty" too, anybody'd get quicker result for that line with: c = 0...

sorry couldnt resist :-)