9 ms·
and gets even worse if you bring variables into the game. a = 5 b = 3 everybody from nearly every programming language would expect that after c = a-b you
by pilot_pirx 14y ago
and gets even worse if you bring variables into the game.
a = 5
b = 3
everybody from nearly every programming language would expect that after
c = a-b
you will find c to be 2 not nil (or throwing an exception or whatever)
- haukur 14y agoI've always found code without spaces around these symbols to be very undreadable.
- pilot_pirx 14y agoYes, but in this case it's not about readability, but about extremely significant whitespace. Forgetting a space and your code has a totally different meaning.
- xyzzyb 14y agoWhitespace is already extremely significant in programming. "foo[1]" vs "foo [1]" for example.
- pilot_pirx 14y agoDepends on language, in Ruby those statements would be identical. But anyway, that's no reason to make things even worse.
- mbrubeck 14y agoIn Ruby those statements are the same when foo is bound to an array, but they are different when foo is bound to a function...
- megablast 14y agoAnd I have found the opposite. Horses for courses.
- nessus42 14y agoI never pack my code like that without whitespace, as doing so is only readable when you have single-letter variables, which is not very common. I agree with the OP. CamelCase and underscores are both scourges.