By Thierry.Lefort
via google-opensource.blogspot.com
Published: Jul 01 2008 / 09:42
Even when you speak the same language as someone else, you may find differences in spelling, pronunciation, or even vocabulary. While the difference between "color" and "colour" isn't likely to confuse anyone, you might run into trouble if your audience doesn't realize that a car's "boot" is the same as its "trunk." Some of us are still trying to figure out whether we wait "on line," "in line," or whether we simply "queue up."
SaveShareSend
Tags: c-and-cpp, methodology
Comments
c0de replied ago:
I find some choices in this guideline to be missing a logical argument.
Why not use exceptions ? What is the argument ? How do you handle errors otherwise, what is your mechanism ?
Why put a space between the reference operator and the variable ? What is the argument ? Is it really more readable ? based on what study ?
I see no reference to templates, you don't use templates at all or anyone can write templates however he wishes ?
Why 2 space indentation ? Why not one space ? Why not three ? Why not tabs and everyone can set the number of spaces in his favorite editor ?
Maybe these are great rules, but please give an argument, explain why these rules are good.
Because otherwise nobody will write code in a way that does not make sense (have no logical argument).
Programming is logic, you can't write logic in an illogical way.
I understand that consistency is the important thing, but why be consistent in somebody's personal taste way and not in a better choice way ?
c0de replied ago:
For the "Why put a space between the reference operator and the variable ?", there is no such thing, I misunderstood the first comment in the article.
Voters For This Link (10)
Voters Against This Link (1)