YafaRay use Allman indentation style (see http://en.wikipedia.org/wiki/Indent_style#Allman_style).
if (a < b)
YafaRay uses doxygen to generate code documentation.
Brief description example ( to be used on class variables):
vector3d_t camX; //!< Camera x axis
Brief and long description example (to be used on class members):
/** Vector reflection.
* Reflects the vector onto a surface whose normal is \a n
* @param n Surface normal
* @warning \a n must be unit vector!
* @note Lynn's formula: R = 2*(V dot N)*N -V (http://www.3dkingdoms.com/weekly/weekly.php?a=2)
inline vector3d_t& vector3d_t::reflect(const vector3d_t &n)
const float vn = 2.0f*(x*n.x+y*n.y+z*n.z);
x = vn*n.x -x;
y = vn*n.y -y;
z = vn*n.z -z;
"In principle, in subsequent releases, the major number is increased when there are significant jumps in functionality, the minor number is incremented when only minor features or significant fixes have been added, and the revision number is incremented when minor bugs are fixed" Wikipedia http://en.wikipedia.org/wiki/Software_versioning
Despite YafaRay never had a coherent versioning in the past, we stick to that priciple from now on.
after a 0.1.2 official release we could have a 0.1.3 release which only fix bugs on 0.1 tree and we will have a 0.2 tree for new features.