![]() ![]() LOC in Fisheyeįisheye calculates the LOC for the trunk only. Thus, in Fisheye we usually look at the LOC of the trunk, unless we can infer from the context that another branch is more appropriate. ![]() A naive summation of the LOC of all the branches will give a meaningless number that jumps every time a branch is copied to create a new branch. In addition, the nature of branching in SCM applications means that calculating a LOC value for a whole project is not possible. Keep these disadvantages and limitations in mind when using LOC in your work environment. While it can be useful, LOC has some well documented disadvantages. However, the change in LOC over a period of time can be negative if there was a net reduction in the LOC over the period. Neither of these should ever be less than zero. LOC for a file/directory is the total number of lines in the relevant files, while LOC for an author is the number of lines blamed on that author. In Fisheye, blank lines and comment lines are counted toward the total lines of code. LOC is literally the count of the number of lines of text in a file or directory. The number of lines indicates the size of a given file and gives some indication of the work involved. Lines of Code or LOC (also known as Source Lines of Code - SLOC) is a quantitative measurement in computer programming for files that contains code from a computer programming language, in text form. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |