 |
Defining Programming Standards |
|
|
|
CHAPTER 3 : General Principles
3.7 There's no one true styleThere is no such thing as a 'correct' style. There are almost as many styles as there are programmers. Some are more sensible than others, but there is no one style that can be clearly agreed upon as being the best style to use. In reading this book, you will almost certainly strongly disagree with some propositions. On the other hand, you will probably find yourself agreeing wholeheartedly with other points. It is worth keeping in mind that there is likely to be someone else reading the book who has diametrically opposite opinions to yours. Some points may be argued logically and clearly, for example where it is about a point of portability, and some item of style simply will not work with some compilers. Some points are much easier to argue about (and often are!), such as the placing of braces or the use of case in naming. But in the end, one style must be chosen. You have to say, "This is the style that we will use. We have argued over which one to use, and the consensus is that this is it". Doubters and dissenters may have to be persuaded or coerced, for although your style is not perfect, it has been chosen to be standard. A maintenance note: If you happen to be changing a program that does not use your style, then the professional approach is to use the style that the program uses, rather than to use your normal style. Maintaining poor style is difficult enough - maintaining several styles at once is hell!
|
|
|
|
|
||||
