第 1/1 張圖片
C++ Coding Standards: 101 Rules, Guidelines, and Best Practices by John Fuller
最後 1 件
狀況：
最後 1 件 / 賣出 1 件
運費：
所在地：Sparks, Nevada, 美國
送達日期：
估計於 6月27日, 四至 7月2日, 二之間送達 運送地點 43230
退貨：
保障：
請參閱物品說明或聯絡賣家以取得詳細資料。閱覽全部詳情查看保障詳情
（不符合「eBay 買家保障方案」資格）
安心購物
物品細節
- 物品狀況
- Book Title
- C++ Coding Standards: 101 Rules, Guidelines, and Best Practices
- Publication Date
- 2004-11-01
- Pages
- 240
- ISBN
- 0321113586
- Subject Area
- Computers
- Publication Name
- C++ Coding Standards : 101 Rules, Guidelines, and Best Practices
- Publisher
- Addison Wesley Professional
- Item Length
- 9.1 in
- Subject
- Programming Languages / C++
- Publication Year
- 2004
- Series
- C++ In-Depth Ser.
- Type
- Textbook
- Format
- Trade Paperback
- Language
- English
- Item Height
- 0.6 in
- Item Weight
- 14.4 Oz
- Item Width
- 7.2 in
- Number of Pages
- 240 Pages
關於產品
Product Identifiers
Publisher
Addison Wesley Professional
ISBN-10
0321113586
ISBN-13
9780321113580
eBay Product ID (ePID)
30876188
Product Key Features
Number of Pages
240 Pages
Publication Name
C++ Coding Standards : 101 Rules, Guidelines, and Best Practices
Language
English
Publication Year
2004
Subject
Programming Languages / C++
Type
Textbook
Subject Area
Computers
Series
C++ In-Depth Ser.
Format
Trade Paperback
Dimensions
Item Height
0.6 in
Item Weight
14.4 Oz
Item Length
9.1 in
Item Width
7.2 in
Additional Product Features
Intended Audience
Scholarly & Professional
LCCN
2004-022605
Dewey Edition
22
Dewey Decimal
005.13/3
Table Of Content
Preface. 1. Organizational and Policy Issues. Don''t sweat the small stuff. (Or: Know what not to standardize.). Compile cleanly at high warning levels. Use an automated build system. Use a version control system. Invest in code reviews. 2. Design Style. Give one entity one cohesive responsibility. Correctness, simplicity, and clarity come first. Know when and how to code for scalability. Don''t optimize prematurely. Don''t pessimize prematurely. Minimize global and shared data. Hide information. Know when and how to code for concurrency. Ensure resources are owned by objects. Use explicit RAII and smart pointers. 3. Coding Style. Prefer compile- and link-time errors to run-time errors. Use const proactively. Avoid macros. Avoid magic numbers. Declare variables as locally as possible. Always initialize variables. Avoid long functions. Avoid deep nesting. Avoid initialization dependencies across compilation units. Minimize definitional dependencies. Avoid cyclic dependencies. Make header files self-sufficient. Always write internal #include guards. Never write external #include guards. 4. Functions and Operators. Take parameters appropriately by value, (smart) pointer, or reference. Preserve natural semantics for overloaded operators. Prefer the canonical forms of arithmetic and assignment operators. Prefer the canonical form of ++ and --. Prefer calling the prefix forms. Consider overloading to avoid implicit type conversions. Avoid overloading &&, , or , (comma). Don''t write code that depends on the order of evaluation of functionarguments. 5. Class Design and Inheritance. Be clear what kind of class you''re writing. Prefer minimal classes to monolithic classes. Prefer composition to inheritance. Avoid inheriting from classes that were not designed to be base classes. Prefer providing abstract interfaces. Public inheritance is substitutability. Inherit, not to reuse, but to be reused. Practice safe overriding. Consider making virtual functions nonpublic, and public functions nonvirtual. Avoid providing implicit conversions. Make data members private, except in behaviorless aggregates (C-stylestructs). Don''t give away your internals. Pimpl judiciously. Prefer writing nonmember nonfriend functions. Always provide new and delete together. If you provide any class-specific new, provide all of the standard forms (plain, in-place, and nothrow). 6. Construction, Destruction, and Copying. Define and initialize member variables in the same order. Prefer initialization to assignment in constructors. Avoid calling virtual functions in constructors and destructors. Make base class destructors public and virtual, or protected and nonvirtual. Destructors, deallocation, and swap never fail. Copy and destroy consistently. Explicitly enable or disable copying. Avoid slicing. Consider Clone instead of copying in base classes. Prefer the canonical form of assignment. Whenever it makes sense, provide a no-fail swap (and provide it correctly). 7. Namespaces and Modules. Keep a type and its nonmember function interface in the same namespace. Keep types and functions in separate namespaces unless they''re specifically intended to work together. Don''t write namespace usings in a header file or before an #include. Avoid allocating and deallocating memory in different modules. Don''t define entities with linkage in a header file. Don''t allow exceptions to propagate across module boundaries. Use sufficiently portable types in a module''s interface. 8. Templates and Genericity. &n
Synopsis
Every software development team should have and follow a coding standard. It's even better when what the coding standard requires is actually consistent, reasonable, and correct. Coding standards have many advantages: *They improve code quality. This happens automatically when following a good, simple set of guidelines. *They improve development speed, because the programmer doesn't need to always make decisions starting from first principles. *They enhance teamwork by eliminating needless debates on inconsequential issues and by making it easy for teammates to read and maintain each other's code. The coding standards introduced by this book are a collection of guidelines for writing high-quality C++ code. ***They are the distilled conclusions of a rich collective experience of the C++ community. Until now, this body of knowledge has been available only as folklore or spread in bits and pieces throughout books., 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., Every software development team should have and follow a coding standard.It's even better when what the coding standard requires is actually consistent, reasonable, and correct.Coding standards have many advantages: *They improve code quality. This happens automatically when following agood, simple set of guidelines.*They improve development speed, because the programmer doesn't need toalways make decisions starting from first principles.*They enhance teamwork by eliminating needless debates on inconsequentialissues and by making it easy for teammates to read and maintain each other'scode.The coding standards introduced by this book are a collection of guidelines forwriting high-quality C++ code.***They are the distilled conclusions of a rich collective experience of the C++community. Until now, this body of knowledge has been available only asfolklore or spread in bits and pieces throughout books.
LC Classification Number
QA76.73.C153S85 2004
Copyright Date
2005
ebay_catalog_id
4
賣家提供的物品說明
運費與處理費
物品所在地：
Sparks, Nevada, 美國
運送地點
不丹, 中國, 中國台灣, 中國澳門, 中國香港, 中非共和國, 丹麥, 乍德, 也門, 亞塞拜疆共和國, 亞美尼亞, 以色列, 伯利茲, 佛得角群島, 保加利亞, 克羅地亞共和國, 冰島, 列支敦士登, 剛果共和國, 剛果民主共和國, 加拿大, 加納, 加蓬共和國, 匈牙利, 南非, 南韓, 博茨瓦納, 卡塔爾, 印尼, 印度, 危地馬拉, 厄瓜多爾, 厄立特里亞, 吉布提, 吉爾吉斯, 哈薩克, 哥倫比亞, 哥斯達黎加, 喀麥隆, 土庫斯安德凱科斯群島, 土庫曼, 土耳其, 圭亞那, 坦桑尼亞, 埃及, 埃塞俄比亞, 基里巴斯, 塔吉克, 塞內加爾, 塞拉利昂, 塞浦路斯, 塞爾維亞, 塞舌爾, 墨西哥, 多哥, 多明尼加共和國, 奧地利, 孟加拉, 安哥拉, 安圭拉島, 安提瓜和巴布達, 安道爾, 寮國, 尼加拉瓜, 尼日爾, 尼泊爾, 巴哈馬, 巴基斯坦, 巴布亞新畿內亞, 巴拉圭, 巴拿馬, 巴林, 布基納法索, 布隆迪, 希臘, 幾內亞, 德國, 意大利, 愛沙尼亞, 愛爾蘭, 所羅門群島, 拉脫維亞, 挪威, 捷克共和國, 摩洛哥, 摩爾多瓦, 摩納哥, 斐濟, 斯威士蘭, 斯洛伐克, 斯洛文尼亞, 斯里蘭卡, 新加坡, 日本, 智利, 柬埔寨, 格陵蘭, 格雷納達, 格魯吉亞, 梵蒂岡, 比利時, 毛里求斯, 汶萊, 沙特阿拉伯, 法國, 波斯尼亞和黑塞哥維那, 波蘭, 泰國, 津巴布韋, 洪都拉斯, 海地, 湯加, 澳洲, 烏干達, 烏拉圭, 烏茲別克, 牙買加, 特里尼達和多巴哥, 玻利維亞, 瑙魯, 瑞典, 瑞士, 瓦利斯和富圖納群島, 瓦努阿圖, 甘比亞, 百慕達群島, 盧旺達, 盧森堡, 直布羅陀, 科威特, 科特迪瓦（象牙海岸）, 秘魯, 突尼斯, 立陶宛, 約旦, 納米比亞, 紐西蘭, 羅馬尼亞, 美國, 聖基茨-尼維斯, 聖文森和格瑞那丁, 聖盧西亞, 聖馬力諾, 肯亞, 芬蘭, 英國, 茅利塔尼亞, 荷蘭, 莫桑比克, 菲律賓, 萊索托, 葡萄牙, 蒙古, 蒙特色拉特島, 薩爾瓦多, 蘇里南, 西班牙, 西薩摩亞, 貝寧, 贊比亞, 赤道幾內亞, 越南, 開曼群島, 阿拉伯聯合酋長國, 阿曼, 阿根廷, 阿爾巴尼亞, 阿魯巴, 馬來西亞, 馬其頓, 馬拉維, 馬爾代夫, 馬耳他, 馬達加斯加, 馬里, 黎巴嫩, 黑山
排除：
APO/FPO, 伊拉克, 俄羅斯聯邦, 利比亞, 利比利亞, 委內瑞拉, 尼日利亞, 巴西, 巴貝多, 幾內亞比索, 新喀里多尼亞, 法屬圭亞那, 法屬玻里尼西亞, 烏克蘭, 瓜德羅普島, 留尼汪島, 白俄羅斯, 美國領地, 阿富汗, 阿拉斯加／夏威夷, 阿爾及利亞, 馬提尼克島
| 運費與處理費 | 運送地點 | 運送方式 | 運送*查看送達備註 |
|---|---|---|---|
| 免運費 | 美國 | Standard Shipping | 估計於 6月27日, 四至 7月2日, 二之間送達 運送地點 43230 |
| US $5.50（大約 HK$ 42.93） | 美國 | Expedited Shipping | 估計於 6月27日, 四至 7月2日, 二之間送達 運送地點 43230 |
| 處理時間 |
|---|
| 通常會在收到所有款項後的 2 個工作日內發貨。 |
| 稅項 |
|---|
| 賣家將對以下州別的買家收取銷售稅： |
物品編號 285036316038 的銷售稅
物品編號 285036316038 的銷售稅
賣家會對寄往以下各州的物品收取銷售稅：
| 州／省 | 銷售稅稅率 |
|---|
退貨政策
| 收到物品後聯絡賣家的期限： | 退款方式 |
|---|---|
| 30 日 | 退款 |
買家負責支付退貨運費。
賣家信用評價 （463,432）
這件物品（1）
所有物品（463,432）