by Christopher Allen and Julie Moronuki · 1 Jan 2015 · 1,076pp · 67,364 words
at the leftmost margin and proceed from there. Another possible mistake is that you might’ve missed the second - in the -- used to comment out source lines of code. So this code: - learn.hs module Learn where -- First declare the name of our module so it -- can be imported by name in a project
by Mark Lutz · 5 Jan 2011
lines among all program source files in a tree named on the command line, and report totals grouped by file types (extension). A simple SLOC (source lines of code) metric: skip blank and comment lines if desired. """ import sys, pprint, os from visitor import FileVisitor class LinesByType(FileVisitor): srcExts = [] # define in subclass def __init
by Walter Isaacson · 6 Oct 2014 · 720pp · 197,129 words
eventually settled after Microsoft agreed to modify some of its practices. 36. By 2009 the Debian version 5.0 of GNU/Linux had 324 million source lines of code, and one study estimated that it would have cost about $8 billion to develop by conventional means (http://gsyc.es/~frivas/paper.pdf). 37. An
by Scott Berkun · 9 Sep 2013 · 361pp · 76,849 words
each issue. 3 A good summary of the problems with evaluating programming work based on lines of code is at http://en.wikipedia.org/wiki/Source_lines_of_code#Disadvantages. Chapter 11 Real Artists Ship In September 1983, the Apple Macintosh project was far behind schedule. The team was burning out but still had
by Jamie L. Mitchell and Rex Black · 15 Feb 2015
evaluates can be split into two categories: static and dynamic. The following measures are static measures: 1. Line count, including lines of code (LOC) and source lines of code (SLOC) 2. Complexity and structure, including cyclomatic complexity, number of modules and number of GOTO statements 3. Object-oriented metrics, including number of classes, weighted