Hugin Coding Style Guide  Consistent application of a style
makes life easier for everybody. You'll find other people's code
more readable, and they will find your code more readable. While
nobody will tap on your fingers for not following these
conventions to the letter, it is highly recommended that you
familiarize with them and follow them.  History and Status of
this Document  This document started from a discussion on coding
style and consistency. It is currently just a collection of the
wisdom and opinion of Hugin contributors and we won't do hard
enforcement / policing, but it would be nice if we could all
stick to the same convention and make the code more readable and
manageable for everyobdy.  Naming Conventions  Contraction Lists
The list is incomplete.    Document your code (or the code you
are reading and understanding) with doxygen. Doxygen is a useful
tool and can also be used to create other documentation that
just class interface descriptions. It works by prefixing the
function prototypes wi