3 ms·
This looks neat on first glance and on small code samples, but I've had so many messed up whitespaces after merging branches that in the real world this would b
by flohofwoe 13y ago
This looks neat on first glance and on small code samples, but I've had so many messed up whitespaces after merging branches that in the real world this would be just another way to shoot yourself in the foot. I really like python for scripting up into the 10k lines-of-code area, but for bigger projects (and teams with more then - say - 3 coders) I wouldn't even consider a dynamically typed language, let alone a language where intendations and newlines are language constructs.
I don't really find the example at the end of the article much more readable (even though it "cheats" a bit by using the C++11 auto keyword and range-based for loop), on the contrary, the white space on the left side looks more messy then on the right side to me.
C++ code which has a lot of STL containers and complex templates does look ugly though, that's why I prefer to either not use this, or hide it under typedefs and decltypes. I also don't like the new auto keyword very much, the compiler SHOULD complain when someone on the team changes types around.