Get Thinking
A detailed discussion of these questions can be found in the "Appendix A" section on page 466.
Mull It Over
Should you alter the layout of legacy code to conform to your latest code style? Is this a valuable use of code reformatting tools?
A common layout convention is to split source lines at a set number of columns. What are the pros and cons of this? Is it useful?
How detailed should a reasonable coding standard be?
How serious are deviations from the style? How many limbs should be amputated for not following it?
Can a standard become too detailed and restrictive? What would happen if it did?
When defining a new presentation style, how many items or cases need layout rules? What other presentation rules must be provided? List them.
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access