第一章至第六章主要论述C++/C编程风格。难度不高，但是细节比较多。别小看了，提高质量就是要从这些点点滴滴做起。世上不存在最好的编程风格，一切因需求而定。团队开发讲究风格一致，如果制定了大家认可的编程风格，那么所有组员都要遵守。如果读者觉得本书的编程风格比较合你的工作，那么就采用它，不要只看不做。人在小时候说话发音不准，写字潦草，如果不改正，总有后悔的时候。编程也是同样道理。

　　第七章至第十一章是专题论述，技术难度比较高，看书时要积极思考。特别是第七章“内存管理”，读了并不表示懂了，懂了并不表示就能正确使用。有一位同事看了第七章后觉得“野指针”写得不错，与我切磋了一把。可是过了两周，他告诉我，他忙了两天追查出一个Bug，想不到又是“野指针”出问题，只好重读第七章。

-Chapter VI which deal mainly with C++/C programming style. The difficulty is not high, but the details are more common. Not sound like, to improve quality is to start from these bit by bit. Does not exist in the world the best programming style, all due to demand. Pay attention to the same style of team development, if approved of established programming style, then all team members must abide by. If readers think this book is also more programming style of your work, then use it, do not look not do. Pronunciation in childhood are not allowed to speak, write illegible, if not corrected, there is always regret the time. Programming is also the same reason.



Chapter VII to Chapter XI is a thematic exposition of technical difficulty is relatively high, positive thinking when reading. Particularly Chapter VII, "memory management", reading does not mean that understand, does not mean that will be able to understand the proper use. One colleague, after reading Chapter VII of the feel