Herb Sutter,ISO C++標準委員會主席,C++ Users Journal雜誌特邀編輯和專欄作傢;他目前在微軟公司領導NET環境下C++浯言擴展的設計工作除本書外.他還撰寫瞭三本廣受贊譽的圖書:Exceptional C++ Style、Exceptional C++和More Exceptional C++。 .
Andrei Alexandrescu,世界頂級的C++專傢.“C++ Users Journal雜誌的專欄作傢,他的Modem C++ Design—書曾榮獲2001年最佳C++圖朽稱號.書中所開發的Loki已經成為最負盛名的C++程序庫之一。
Consistent, high-quality coding standards improve software quality, reduce time-to-market, promote teamwork, eliminate time wasted on inconsequential matters, and simplify maintenance. Now, two of the world's most respected C++ experts distill the rich collective experience of the global C++ community into a set of coding standards that every developer and development team can understand and use as a basis for their own coding standards. The authors cover virtually every facet of C++ programming: design and coding style, functions, operators, class design, inheritance, construction/destruction, copying, assignment, namespaces, modules, templates, genericity, exceptions, STL containers and algorithms, and more. Each standard is described concisely, with practical examples. From type definition to error handling, this book presents C++ best practices, including some that have only recently been identified and standardized-techniques you may not know even if you've used C++ for years. Along the way, you'll find answers to questions like * What's worth standardizing--and what isn't? * What are the best ways to code for scalability?* What are the elements of a rational error handling policy? * How (and why) do you avoid unnecessary initialization, cyclic, and definitional dependencies?* When (and how) should you use static and dynamic polymorphism together?* How do you practice "safe" overriding?* When should you provide a no-fail swap? * Why and how should you prevent exceptions from propagating across module boundaries?* Why shouldn't you write namespace declarations or directives in a header file?* Why should you use STL vector and string instead of arrays?* How do you choose the right STL search or sort algorithm?* What rules should you follow to ensure type-safe code? Whether you're working alone or with others, C++ Coding Standards will help you write cleaner code--and write it faster, with fewer hassles and less frustration.
我看过了 我看过了 我看过了 我看过了 我看过了 我看过了 我看过了 我看过了 我看过了 我看过了 我看过了 我看过了 我看过了 我看过了 我看过了 我看过了 我看过了 我看过了 我看过了 我看过了 我看过了 我看过了 我看过了 我看过了 我看过了 我看过了 我看过了 我看过了 我看...
評分光买了书,唉没时间看书啊!我电脑Z差啊,学得头都大了啊!还好,室友告诉我上猎豹网校,看那个视频课程学。嘿嘿,这是个简单容易的办法!这下不再担心买了书,束之高阁了!
評分比较轻量级的一本书。如果你已经看过 effective c++ ,exceptional c++系列,那这本书只用翻翻目录就行了。
評分其实这本书很鸡肋。因为此书是对一条条的规范、原则、实践等的高度提炼,能力到了自然能理解,能力没到看完也不一定能理解,此时你需要类似《Unix编程艺术》的书,当然你仍然需要足够的实践来支持,要不就会像我一样在这里说大话! 如果你是完美主义者,如果你本来就注重思维...
評分其实这本书很鸡肋。因为此书是对一条条的规范、原则、实践等的高度提炼,能力到了自然能理解,能力没到看完也不一定能理解,此时你需要类似《Unix编程艺术》的书,当然你仍然需要足够的实践来支持,要不就会像我一样在这里说大话! 如果你是完美主义者,如果你本来就注重思维...
水平不夠,examples的論證太弱又不想去滿地翻quotation,結果就是不少觀點都不明所以。
评分水平不夠,examples的論證太弱又不想去滿地翻quotation,結果就是不少觀點都不明所以。
评分水平不夠,examples的論證太弱又不想去滿地翻quotation,結果就是不少觀點都不明所以。
评分講解太簡略,有時候不太準確,幾乎沒有示例。用來查缺補漏和迴顧很不錯。
评分遵從KISS原則:Correct is better than fast.Simple is better than complex. Clear is better than cute. Safe is better than insurance.還有一些design principle 比如single responsibility,least surprise,open/close balabala 一邊寫一邊悟吧。。
本站所有內容均為互聯網搜索引擎提供的公開搜索信息,本站不存儲任何數據與內容,任何內容與數據均與本站無關,如有需要請聯繫相關搜索引擎包括但不限於百度,google,bing,sogou 等
© 2025 book.quotespace.org All Rights Reserved. 小美書屋 版权所有