Report the version number of SLOCCount and immediately exit.
This option cant be usefully combined with any other option.
Do not recalculate; instead, use cached results from a previous execution.
Without the --cached or --append option,
sloccount automatically removes the data directory
and recreates it.
Do not remove previous calculations from the data directory;
instead, add the analysis to the current contents of the data directory.
Store or use cached data in the given data directory; default value
Follow symbolic links.
Count all duplicates.
Normally, if files have equal content (as determined using
MD5 hash values), only one is counted.
Count duplicates if they occur in different portions of the breakdown.
Thus, if the top directory contains many different projects, and you
want the duplicates in different projects to count in each project,
choose this option.
Count source code files that appear to be automatically generated.
Normally these are excluded.
The different directories represent different projects;
otherwise, its assumed that all of the source code belongs
to a single project.
This doesnt change the total number of files or SLOC values, but
it does affect the effort and schedule estimates.
Given this option,
effort is computed separately for each project (and then summed),
and the schedule is the estimated schedule of the largest project.
Display counts of files instead of SLOC.
Display in the "wide" (tab-separated) format.
Display details, that is, results for every source code file.
|--effort F E|
Change the factor and exponent for the effort model.
Effort (in person-months) is computed as F*(SLOC/1000)^E.
|--schedule F E|
Change the factor and exponent for the schedule model.
Schedule (in months) is computed as F*(effort)^E.
Change the average annual salary to
Change the overhead value to
overhead. Estimated cost is computed as effort * personcost * overhead.
Add a language not considered by default to be a language to be
Currently the only legal values for language are "makefile", "sql",
are not normally included in the SLOC counts, although their SLOCs are
internally calculated and they are shown in the file counts.
If you want to include more than one such language, do it by
passing --addlang more than once, e.g., --addlang makefile --addlang sql.
Add all languages not normally included in final reports.
As with many other programs using Unix-like options, directories whose names begin with a dash (-) can be misinterpreted as options. If the directories to be analyzed might begin with a dash, use the double-dash (- -) to indicate the end of the option list before listing the directories.
Filenames with embedded newlines (in the directories or their descendants) wont be handled correctly; they will be interpreted as separate filenames where the newlines are inserted. An attacker could prevent sloccount from working by creating filenames of the form /normal/directory ... NEWLINE/dev/zero. Such filenames are exceedingly rare in source code because theyre a pain to work with using other tools, too. Future versions of sloccount may internally use NUL-separated filenames (like GNU finds -print0 command) to fix this.
There are many more languages not yet handled by SLOCCount.
SLOCCount only reports physical source lines of code. It would be very useful if it could also report logical lines of code, and perhaps other common metrics such as McCabes complexity measures and complexity density (complexity/SLOC for each function or procedure).
See the SLOCCount website at http://www.dwheeler.com/sloccount. Note that more detailed documentation is available both on the website and with the SLOCCount package.
David A. Wheeler (firstname.lastname@example.org).
|SLOCCount||SLOCCOUNT (1)||31 July 2004|