Style

TODO: style unification has been planned around version 4.0.0

Coding style

• use spaces instead of tabs
• try to keep at lines no longer than 80 characters
• use lower-case names and words separated with underscore for types, functions and objects
• use CamelCase names for template parameters (i.e. OutputIterator, T)
• all private members should have underscore suffix
• all code and comments should be written in English

Guidelines

• be consistent
• prefer good clear self-descriptive names, instead of short cryptic and obscure names
• prefer explicit expression of your intention over implicit and obscure
• if in doubt, look at the code of soci/src/core
  • if still in doubt, look at source code of Boost C++ Libraries and Boost Library Requirements and Guidelines
  • if still in doubt, ask on the mailing lists