>My biggest problem(s) with the '{' are that
>1) They're WAY too easy to lose track of. If you absolutely must have something to designate the beginning and ending for a code chunk, what's wrong with 'begin' and 'end'? Much easier to keep track of
>2) The fact that, because of 1, people will put them on separate lines, increasing the white space in a program and (to me) making it more difficult to read and to follow the logic flow. I have the same issue when people comment out huge swathes of code rather than remove it after a set period of time. Seriously, we've got programs that have 100's of lines that were commented out in 2005.


Note: These look better if you download the project and look at it using an editor which uses 4 spaces for tabs (https://github.com/RickCHodgin/libsf and download the ZIP along the right).

Not all C code is difficult to read (beginning around line 200):
https://github.com/RickCHodgin/libsf/blob/master/utils/sha1/sha1.cpp

And:
https://github.com/RickCHodgin/libsf/blob/master/vvm/core/vfrp/vfrp_sup.cpp

Interspersed comments, using a particular indentation sequence... these can make for consistently readable code.