Source lines of code: Difference between revisions

Revision as of 15:19, 22 June 2019

Revision as of 16:12, 22 June 2019

Line 166:

# Scope for automation of counting: since line of code is a physical entity, manual counting effort can be easily eliminated by automating the counting process. Small utilities may be developed for counting the LOC in a program. However, a logical code counting utility developed for a specific language cannot be used for other languages due to the syntactical and structural differences among languages. Physical LOC counters, however, have been produced which count dozens of languages.

# An intuitive metric: line of code serves as an intuitive metric for measuring the size of software because it can be seen, and the effect of it can be visualized. [[Function points]] are said to be more of an objective metric which cannot be imagined as being a physical entity, it exists only in the logical space. This way, LOC comes in handy to express the size of software among programmers with low levels of experience.

# Ubiquitous measure: LOC measures have been around since the earliest days of software<ref>IFPUG [http://www.{{citationifpug.org/Documents/Jones-LinesofCodeMetricV6.pdf needed|date=November"a 2014}}short history of lines of code (loc) metrics"]</ref>. As such, it is arguable that more LOC data is available than any other size measure.

=== Disadvantages ===