|Eingestellt in Kategorie:
Ähnlichen Artikel verkaufen?

C ++ Codierungsstandards: 101 Regeln, Richtlinien und Best Practices von John Fuller

Letzter Artikel
Artikelzustand:
Gut
Letzter Artikel / 1 verkauft
Preis:
US $7,93
Ca.CHF 7,09
Versand:
Kostenlos Standard Shipping. Weitere Detailsfür Versand
Standort: Sparks, Nevada, USA
Lieferung:
Lieferung zwischen Do, 27. Jun und Mo, 1. Jul nach 43230 bei heutigem Zahlungseingang
Liefertermine - wird in neuem Fenster oder Tab geöffnet berücksichtigen die Bearbeitungszeit des Verkäufers, die PLZ des Artikelstandorts und des Zielorts sowie den Annahmezeitpunkt und sind abhängig vom gewählten Versandservice und dem ZahlungseingangZahlungseingang - wird ein neuem Fenster oder Tab geöffnet. Insbesondere während saisonaler Spitzenzeiten können die Lieferzeiten abweichen.
Rücknahmen:
30 Tage Rückgabe. Käufer zahlt Rückversand. Weitere Details- Informationen zu Rückgaben
Zahlungen:
     

Sicher einkaufen

eBay-Käuferschutz
Geld zurück, wenn etwas mit diesem Artikel nicht stimmt. 

Angaben zum Verkäufer

Angemeldet als gewerblicher Verkäufer
Der Verkäufer ist für dieses Angebot verantwortlich.
eBay-Artikelnr.:285036316038
Zuletzt aktualisiert am 22. Jun. 2024 13:06:50 MESZAlle Änderungen ansehenAlle Änderungen ansehen

Artikelmerkmale

Artikelzustand
Gut: Buch, das gelesen wurde, sich aber in einem guten Zustand befindet. Der Einband weist nur sehr ...
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
Author
Andrei Alexandrescu, Herb Sutter
Item Weight
14.4 Oz
Item Width
7.2 in
Number of Pages
240 Pages

Über dieses Produkt

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
Author
Andrei Alexandrescu, Herb Sutter
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

Artikelbeschreibung des Verkäufers

AlibrisBooks

AlibrisBooks

98,5% positive Bewertungen
1.8 Mio. Artikel verkauft
Shop besuchenKontakt

Detaillierte Verkäuferbewertungen

Durchschnitt in den letzten 12 Monaten

Genaue Beschreibung
4.9
Angemessene Versandkosten
4.9
Lieferzeit
4.9
Kommunikation
4.9
Angemeldet als gewerblicher Verkäufer

Verkäuferbewertungen (463'406)

s***o (63)- Bewertung vom Käufer.
Letzter Monat
Bestätigter Kauf
Thanks!
Alle Bewertungen ansehen