Examples:

qdmet /s root=../develop/bxlib files=*.cpp;*.h

qdmet root=c:\src\xproj /s

qdmet /s

Additionally, three derivatives of the above are listed (only in the log file, not in the screen output):

• Number of comment lines per line of code;
• Fraction of empty lines among all lines;
• Terminators (semicolons) per code line;
• Characters per code line.

Actually, these four my say something on the coding style, and it is quite interesting to compare them between programmers.

Remarks:

1. If a line contains both code and comment, it will be counted in both line categories. Thus, the code

   x = sin(t+0.0001); // safety margin

   will be counted the same way as

   x = sin(t+0.0001);
   // safety margin

2. In character count, any leading and trailing spaces are stripped from the line, and multiple spaces are merged. For example, the line

      x = z   +   t  -  1;     // ???

   will result in the same character count as

   x = z + t - 1; // ???

   but _not_ in the same as

   x=z+t-1;//???

   This prevents the worst possible abuse of gaming the system; a better approach (which I may consider in a future version) may distinguish between "meaningful" and "non-meaningful" space, so that the third example would yield identical result as the others.

3. Code lines containing just one character are counted as empty lines. This removes a great dependency of line counting on code layout preferred by various programmers. For example, the snippet

   if (x>0)
   {
      callCounter(x);
   }

   will be counted as two code lines, the same as

   if (x>0)
      callCounter(x);

   Of course, this does not remove all layout style dependency: the fragment

   if (x>0) callCounter(x);

   will still be counted as one code line.