[Pharo-project] linesOfCode or another simple/understandable metric vaguely related to 'effort'

Stefan Marr smalltalk at stefan-marr.de
Sun Jan 8 08:03:06 EST 2012

Hi Janko, Mariano:

On 04 Jan 2012, at 23:34, Janko Mivšek wrote:
>>    http://www.squeaksource.com/WebCodeStats.html

I derived the following from your WebCodeStats:

-------------- next part --------------
A non-text attachment was scrubbed...
Name: ClassStats.st
Type: application/octet-stream
Size: 5187 bytes
Desc: not available
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20120108/eb40b88b/attachment.st>
-------------- next part --------------

I needed a bit more flexibility in terms of what to measure.
Monticello package are to coarse grained, and I needed to handle extension methods separately, too.

To have another number in addition to LOC, I also added the number of bytecodes.
That number is less volatile to comments and white spaces. Thus, it should correlate slightly better with the 'complexity' aspect of the code. While LOC represents, as good as it can, 'maintainability'.

Disclaimer: It is neither polished nor beautiful, and at least the #isOmniSelector call is specific to my stuff.

But, well, might be useful start for someone out there.

Best regards

Stefan Marr
Software Languages Lab
Vrije Universiteit Brussel
Pleinlaan 2 / B-1050 Brussels / Belgium
Phone: +32 2 629 2974
Fax:   +32 2 629 3525

More information about the Pharo-dev mailing list