"Readability and understandability of code is not just an issue of code formatting: is it?"
actually, it is. high level management, "dive in without seeing it before" contractors, and people who don't want to read piles of docs before getting something done, prefer "readable code".
The most readable style of all is Allman Style. It has a lot of white space in it, which means that you can clearly see where the boundaries are. It works best if you enforce curly braces around things like this:
(using dots instead of white space - the editor doesn't represent them properly)
even though a lot of people might be tempted to:
The first example is MORE READABLE. A coder might not like it because it "takes up too much space on the screen" but too bad. For someone skimming code [not reading every! single! line! and! detail!] it's a LOT easier to see things this way. It's *EFFICIENT* in other words, for reasons not obvious to the K&R fascists nor to the hard-tab nazis. Oh yeah, no hard tabs either. Then your tab settings won't affect what it looks like...
/me wants to be able to view it with 'less' and have everything line up EXACTLY! THE! SAME! as it does in an IDE, or a simple editor like 'nano', or a GUI editor like 'pluma', or something like vi, or whatever.
graphic being 'style nazi' alert this time