Posts by Brian Downing

Topic: SBCL code badly miscounted

SBCL is missing most of its source code from its Ohloh project page (http://www.ohloh.net/projects/5299). None of the Lisp code is counted, despite other projects written in Lisp being counted. This is what I posted about it about 20 days ago in the "Mostly Written In..." thread:

SBCL (http://www.ohloh.net/projects/5299) is written in Common Lisp, but Ohloh says it's primarily written in C/C++. We have C components:

:; find . -name '*.[ch]' | xargs wc -l | tail -1
  34115 total

but they are dwarfed by the amount of code in Lisp:

:; find . -name '*.lisp' | xargs wc -l | tail -1
  395570 total

Commits to .lisp files don't seem to be counted as Lisp either. In fact, those 400,000 lines of code don't even show up in the code report: http://www.ohloh.net/projects/5299/analyses/latest

Also:

By the way, if you want to try and differentiate Common Lisp from random generic Lisp, Common Lisp sources usually have a line that looks like one of these:

(in-package :cl-user)
(CL:IN-PACKAGE "MY-PACKAGE")
(common-lisp:in-package #:this-is-rather-long)

so maybe looking for a line like:

/^\(([^\)]*:)?in-package\s/i

would be a decent tact? It won't get everything, but it'll get a lot. There's no standard for file extensions, but *.lisp is quite common, *.cl is also used, and I believe *.lsp is used by 8.3 holdovers.

SBCL in addition uses *.lisp-expr for single Lisp expressions, but if those didn't get counted it wouldn't be the end of the world.

It's a little frustrating that the project is only listed as a tenth of the size it really is, especially since other Lisp code in other projects seems to get counted.

Topic: Mostly Written In...

By the way, if you want to try and differentiate Common Lisp from random generic Lisp, Common Lisp sources usually have a line that looks like one of these:

(in-package :cl-user)
(CL:IN-PACKAGE "MY-PACKAGE")
(common-lisp:in-package #:this-is-rather-long)

so maybe looking for a line like:

/^\(([^\)]*:)?in-package\s/i

would be a decent tact? It won't get everything, but it'll get a lot.

There's no standard for file extensions, but *.lisp is quite common, *.cl is also used, and I believe *.lsp is used by 8.3 holdovers.

Topic: Mostly Written In...

SBCL (http://www.ohloh.net/projects/5299) is written in Common Lisp, but Ohloh says it's primarily written in C/C++.

We have C components:

:; find . -name '*.[ch]' | xargs wc -l | tail -1
  34115 total

but they are dwarfed by the amount of code in Lisp:

:; find . -name '*.lisp' | xargs wc -l | tail -1
  395570 total

Commits to .lisp files don't seem to be counted as Lisp either.

In fact, those 400,000 lines of code don't even show up in the code report:

http://www.ohloh.net/projects/5299/analyses/latest