Get Thinking
A detailed discussion of the following questions can be found in the "Appendix A" section on page 474.
Mull It Over
Are these good variable names? Answer with either yes (explain why, and in what context), no (explain why), or can’t tell (explain why).
int apple_countchar foobool apple_countchar *stringint loop_counter
When would these be appropriate function names? Which return types or parameters might you expect? Which return types would make them nonsensical?
doIt(...)value(...)sponge(...)isApple(...)
Should a naming scheme favor the easy reading or easy writing of code? How would you make either easy?
How many times do you write a single piece of code? (Think about it.) How many times do you read it? Your answers should give some indication ...
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