• const-correctness help

• Back to DeveloperResources.

• details labeled ENFORCED are checked and forced by source testing mechanisms.

C++ Guidelines

Source formatting guidelines

• We have an astyle wrapper that formats the code without breaking it.

• If you have astyle version 1.23 please format your changes with ~/scripts/formater.pl
• This formatter is run regularly over the entire code to enforce certain checkable guidelines but it helps reduce trouble if your code matches those guidelines when submitted.

ENFORCED:

• 4-space indentation, no tabs

• no trailing whitespace on any line

• one space between if and its parameter () brackets

• construct open braces { begin on the same line as their construct (if, while)

NP: The formatter is known to enforce some weird indentation at times. Notably after #if ... #endif directives. If you find these, please ignore for now. They will be corrected in a later version of the formatter.

Mandatory coding rules

• Document, at least briefly, every new type, class, member, or global. Doxygen format is appreciated.
• The Big Three: Every class that has one of (Destructor, copy constructor, assignment operator) must have all three. This includes base and derived classes.

• Naming conventions as covered in Features/SourceLayout are to be used.

Suggested coding rules

• Use internally consistent naming scheme (see below for choices).

• Words in global names and all type names are CamelCase capitalized:

  • including the first word.
  • acronyms are to be downcased to fit (ie Http)
  • This includes class types, global variables, static class members, and macros.
• Use const qualifiers in declarations as much as appropriate.
• Use bool for boolean types.
• Avoid macros.
• Do not start names with an underscore

Word capitalization example

  class ClassStats;

  class ClassName {
  public:
    static ClassStats &Stats();

    void clear();

  private:
    static ClassStats TheStats;
    int theInternalState;
  };

  extern void ReportUsage(ostream &os);

Class declaration layout

  class Foo{
  public:
    static methods
    member methods

    static variables
    member variables

  protected:
    static methods
    member methods

    static variables
    member variables

  private:
    static methods
    member methods

    static variables
    member variables
  };

Member naming

Pick one of the applicable styles described below and stick to it. For old classes, try to pick the style which is closer to the style being used.

Explicit accessors:

      void setMember(const Member &);
      const Member &getMember() const; // may also return a copy
      Member &getMember();
      bool hasMember() const;

Compact accessors:

      void member(const Member &);
      const Member &member() const; // may also return a copy
      Member &member();
      bool hasMember() const;

Private data members using underscore suffix (may look C-ish)

      int counter_;
      int next_;
      bool clean_;
      bool sawHeader_;

Private data members using the/verb prefix (may clash with method names)

      int theCounter;
      int theNext;
      bool isClean;
      bool sawHeader;

State checks prefixed with an appropriate verb. Avoid negative words because double negation in if-statements will be confusing; let the caller negate when needed.

      bool canVerb() const;
      bool hasNoun() const;
      bool haveNoun() const; // if class name is plural
      bool isAdjective() const; // but see below

      bool notAdjective() const; // XXX: avoid due to !notAdjective()

The verb is may be omitted, especially if the result cannot be confused with a command (the confusion happens if the adjective after is can be interpreted as a verb):

      bool isAtEnd() const; // OK, but excessive
      bool atEnd() const; // OK, no confusion

      bool isFull() const;  // OK, but excessive
      bool full() const;  // OK, no confusion

      bool clear() const; // XXX: may look like a command to clear state
      bool empty() const; // XXX: may look like a "become empty" command

File #include guidelines

.cc

• include either config.h or squid.h as their first include
  • config.h - minimal dependency include. Intended for use outside of src/. This contains very little beyond the portability requirements.
  • squid.h - full squid dependency tree include (globals, protos, types, defines, everything is in here)

.h and .cci

• DO NOT include either config.h or squid.h

all

• place internal header includes above system includes
• reference internal includes by their full internal path (may exclude src/ from path)
• sort internal includes alphabetically
• minimal system includes
• wrap system includes in autoconf HAVE_FILE_H protection macros
• sort system includes alphabetically
  • should import order-dependent headers through libcompat

Preferred include layout:

// required first include
#include "config.h"

// local source files alphabetically sorted
#include "cutom.h"
#include "local.h"

// System includes alphabetically sorted and wrapped
#if HAVE_ACCESS_H
#include <access.h>
#endif
#if HAVE_STDLIB_H
#include <stdlib.h>
#endif

Component Macros in C++

Squid uses autoconf defined macros to eliminate experimental or optional components at build time.

• name in C++ code should start with USE_
• should be tested with #if and #if ! rather than #ifdef or #ifndef
• should be wrapped around all code related solely to a component; including compiler directives and #include statements

ENFORCED:

• MUST be used inside .h to wrap relevant code.

Automake Syntax Guidelines

Makefile substitution variables

ENFORCED:

• Makefile.am must use the $(DEFAULT_FOO) form for autoconf variables passed with AC_SUBST(DEFAULT_FOO).

File naming

• .h files should only declare one class or a collection of simple, closely related classes.
• No two file names that differ only in capitalization

• For new group of files, follow Features/SourceLayout

ENFORCED:

• .h files MUST be parseable as a single translation unit
  (ie it includes it's dependent headers / forward declares classes as needed).

Component Macros in Automake

Squid uses autoconf defined macros to eliminate experimental or optional components at build time.

• name for variables passed to automake code should start with ENABLE_

Example usage:

if ENABLE_FOO
FOO_SRC=foo.h foo.cc
FOO_LIBS=foo.la
else
FOO_SRC=
FOO_LIBS=
endif

squid_SOURCES= $(FOO_SRC) ...
LDADD = $(FOO_LIBS)

Autoconf Syntax Guidelines

The current standard for both --enable and --with flags is:

• yes means force-enable, fail the build if not possible.

• no means force-disable,

• auto means try to enable, disable if some required part is not available.

For --with flags, everything else is usually considered as a path to be used. Though in some cases is a global constant.

For --enable flags, may contain a list of the components modular pieces to be enabled. In which case:

• being listed means force-enable
• being omitted means force-disable

For further details on autoconf macros and conventions, also see Features/ConfigureInRefactoring

Component Macros in Autoconf

Squid uses autoconf defined macros to eliminate experimental or optional components at build time.

• name for variables passed to automake code should start with ENABLE_
• name for build/no-build variables passed to C++ code should start with USE_
• name for variables passed to either automake or C++ containing default values should start with DEFAULT_

  In the event of a clash or potential clash with system variables tack SQUID_ after the above prefix. ie ENABLE_SQUID_ or USE_SQUID_

# For --enable-foo / --disable-foo

AC_CONDITIONAL([ENABLE_FOO],[test "x${enable_foo:=yes}" = "xyes"])

SQUID_DEFINE_BOOL(USE_FOO,${enable_foo:=no},[Whether to enable foo.])

DEFAULT_FOO_MAGIC="magic"
AC_SUBST(DEFAULT_FOO_MAGIC)

C source guidelines

The only remaining C sources are in third-party code. Follow their standard from surrounding code.

• Remember to update the third-party changelog.

As per Squid2CodingGuidelines.