| Home | Libraries | People | FAQ | More

# Boost Header Policy

Header files are the place where a library comes into contact with user code and other libraries. To co-exist peacefully and productively, headers must be "good neighbors".

Here are the standards for namespace boost headers. Many of these are also reasonable guidelines for general use.

- Headers should have a .hpp (lowercase) filename extension.
- Wrap the header in #ifndef guards so that multiple inclusion is benign. Use a naming convention that minimizes the chance of clashes with macro names from other's code. The sample header uses the Boost convention of all uppercase letters, with the header name prefixed by the namespace name, and suffixed with HPP, separated by underscores.
- Wrap the header contents in a namespace to prevent global namespace pollution. The namespace approach to pollution control is strongly preferred to older approaches such as adding funny prefixes to global names. Libraries which are designed to work well with other Boost libraries should be placed namespace `boost`.
- Place the header file in a sub-directory to prevent conflict with identically named header files in other libraries. The parent directory is added to the compiler's include search path. Then both your code and user code specifies the sub-directory in `#include` directives. Thus the header sample header would be included by `#include <boost/furball.hpp>`
- The preferred ordering for class definitions is public members, protected members, and finally private members.
- Include the boost/config.hpp configuration header if there is a need to deal with compiler or platform configuration issues.

## Sample Header

    //  Boost general library furball.hpp header file  ---------------------------//

    //  (C) Copyright Your Name 1998. Permission to copy, use, modify, sell and
    //  distribute this software is granted provided this copyright notice appears
    //  in all copies. This software is provided "as is" without express or implied
    //  warranty, and with no claim as to its suitability for any purpose.

    //  See http://www.boost.org for updates, documentation, and revision history.

    #ifndef BOOST_FURBALL_HPP
    #define BOOST_FURBALL_HPP

    namespace boost {

    //  Furball class declaration  -----------------------------------------------//

      class furball
      {
        public:
          void throw_up();
        private:
          int whatever;
      };  // furball

    } // namespace

    #endif  // BOOST_FURBALL_HPP

## Coding Style

The alert reader will have noticed that the sample header employs a certain coding style for indentation, positioning braces, commenting ending braces, and similar formatting issues. These stylistic issues are viewed as personal preferences and are not part of the Boost Header Policy.

Revised 06 February, 2001