View previous topic :: View next topic
|
Author |
Message |
gnaveenkumar.99
New User
Joined: 21 Sep 2011 Posts: 8 Location: India
|
|
|
|
What is meant by SLOC count? What is the use of this SLOC count? How do we count it? Do we have any tools to count the SLOC? |
|
Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007 Posts: 10873 Location: italy
|
|
|
|
what happened when You googled for it!
no need for anybody to rewrite what can be found easily with a simple search
Quote: |
Source lines of code - Wikipedia, the free encyclopedia
en.wikipedia.org/wiki/Source_lines_of_codeSource lines of code (SLOC) is a software metric used to measure the size of a software program by counting the number of lines in the text of the program's ...
Measurement methods - Origins - Usage of SLOC measures
SLOCCount
Use [URL] BBCode for External Links is the home page of "SLOCCount", a set of tools for counting physical Source Lines of Code (SLOC) in a large number of languages of a potentially large ... |
/pickiness on
SLOC count is useless repetition ( the last C stands for count ) - but it might increase the published productivity
like in Personal PIN ( heard it too many times ) - but it might increase security level |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello,
Many individual organizations have been unable to completely define/accept precicely what is a "source line of code".
There is no true industry standard that i'm aware of. And probably there is no need for one. |
|
Back to top |
|
|
Ed Goodman
Active Member
Joined: 08 Jun 2011 Posts: 556 Location: USA
|
|
|
|
Enrico,
The "C" is "Code" not "Count"
TS,
The definition of anything like SLOC is that you have accountants in charge in stead of technical folks. The best thing to do is ask back up the chain for their definition of SLOC, so you can follow it.
Trust me, put three of those creatures in a room and ask them that question, and you'll lose all faith in humanity. |
|
Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007 Posts: 10873 Location: italy
|
|
Back to top |
|
|
Ed Goodman
Active Member
Joined: 08 Jun 2011 Posts: 556 Location: USA
|
|
|
|
To give you an IDEA of what it MIGHT mean, take a look at an Enterprise COBOL compile listing.
There is a count given that looks like:
Code: |
* Procedure Division statements = 24 |
That is the number of STATEMENTS in the program logic.
As you can well imagine, if people are getting paid by the statement, people will write more statements. Also, a small program may be a better program, worth more money to a company in the long run. So this SLOC stuff is just a way for non-technicals to try and get a handle on "how big" a system is.
Think about the PERL language. You've seen those filtering expressions that look like cussing in a comic strip:
url: = F(*(65$#$#$$##@@!@##$|||\\\\\\\\\\\\\\
That one line of code can replace HUNDREDS of code lines if written as IF/THEN statements. |
|
Back to top |
|
|
Akatsukami
Global Moderator
Joined: 03 Oct 2009 Posts: 1788 Location: Bloomington, IL
|
|
|
|
Ed Goodman wrote: |
Think about the PERL language. You've seen those filtering expressions that look like cussing in a comic strip:
url: = F(*(65$#$#$$##@@!@##$|||\\\\\\\\\\\\\\
That one line of code can replace HUNDREDS of code lines if written as IF/THEN statements. |
Is then Perl, like APL, a write-only language? |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
|
|
|
|
Perl is a DANGEROUS language (and I say that even though I use it regularly)! It is quite powerful but with plenty of side effects and hidden gotchas. |
|
Back to top |
|
|
|