Jump to content

Optimizing C++/Guidelines for editors

Add links
From Wikibooks, open books for an open world
Optimizing C++
Cover
  1. Introduction
  2. Optimization life cycle
  3. Writing efficient code
    1. Performance improving features
    2. Performance worsening features
    3. Constructions and destructions
    4. Allocations and deallocations
    5. Memory access
    6. Thread usage
  4. General optimization techniques
    1. Input/Output
    2. Memoization
    3. Sorting
    4. Other techniques
  5. Code optimization
    1. Allocations and deallocations
    2. Run-time support
    3. Instruction count
    4. Constructions and destructions
    5. Pipeline
    6. Memory access
    7. Faster operations

Conventions

[edit | edit source]

This is the local manual of style (WB:LMOS) for the Optimizing C++ Wikibook.

These conventions are not part of the book, and therefore are to be omitted from the PDF version of the book. They are only directives for contributors (aka editors).

This wikibook, after introductory chapters, contains three sets of programming guidelines:

  • C++ specific guidelines to be applied at design-time or first-implementation-time.
  • Language independent guidelines to be applied in bottlenecks at optimization-time, with examples in C++.
  • C++ specific guidelines to be applied in bottlenecks at optimization-time.

Every guideline has the following format:

  • Mnemonic title. It has a Title 3 style.
  • Rule, having the following style: "When you are in this situation, do this.". It is in bold type.
  • Minimal example of C++ code.
  • Rationale.

The C++ programming style is loosely that used in the books written by Bjarne Stroustrup.

There are no comparisons with other programming languages, except the C language.

Every guideline specifies exactly when it is to be applied, and what the programmer has to do to apply it.

Little reference is done to compiler optimization technology.

Only the most general and useful algorithms are mentioned.

Little reference is done to specific computer architectures, compilers, and operating systems.

The following terms are used:

  • Member function, instead of method.
  • Member variable, instead of instance variable.
  • Function, instead of routine or procedure. The word routine is used only for machine language code.
  • Argument, instead of parameter, for functions declarations, definitions or calls.
  • Parameter, instead of argument, for templates definitions or instantiations.
Retrieved from "https://en.wikibooks.org/w/index.php?title=Optimizing_C%2B%2B/Guidelines_for_editors&oldid=3341531"