sloc

How can I graph the Lines of Code history for git repo?

Basically I want to get the number of lines-of-code in the repository after each commit. The only (really crappy) ways I have found is to use git filter-branch to run "wc -l *", and a script that run git reset --hard on each commit, then ran wc -l To make it a bit clearer, when the tool is run, it would output the lines of code of the ...

How many SLOCs are you managing in your current work?

Right now I'm directly responsible for around 120k of Java code, about 3/5 is written using GWT. I can trace any functionality to a source file in less than 1min/30 secs. I have 3 years of professional experience and an academic degree. I was wondering what is the average of SLOCs that an average developer is directly responsible for (I...

Counting Line Numbers in Eclipse

I have a Java project in Eclipse with ~10 packages and ~10 class files per package. Is there a way to determine total lines of code for the whole project from within Eclipse? I am familiar with other tools (e.g., Code Analyzer, wc, etc.) but I want to know if there is a way to do this within Eclipse (or get confirmation that there is n...

Implied meaning of Ratio of Physical to Logical SLOC

Hi, If there any implied meaning of a high or low ratio of Physical to Logical SLOC? Does it means anything like bad programming style or something merits consideration? Below is the metric of our codebase got from CodeCount. It is good or bad ratio ? Or it does not matter. 1510738 CODE Physical 889284 CODE Logical Ratio o...

Article about code density as a measure of programming language power

I remember reading an article saying something like "The number of bugs introduced doesn't vary much with different programming languages, but it depends pretty much on SLOC (source lines of code). So, using the programming language that can implement the same functions with smaller SLOC is preferable in terms of stability." The au...

How bad is SLOC (source lines of code) as a metric?

We are documenting our software development process. For technical people, this is pretty easy: iterative development with internal milestones every four weeks, external every 3 months. However, the purpose of this exercise is to expose things for our project management in terms that they can understand. Specifically, these non-tech...