I don't know if anyone has had the time to calculate the metrics for SSDS source code. Inspired by spenk's Facts Only attitude, I decided it was about time someone did. I found a Metrics calculator able to handle Visual Basic (SourceMonitor by Campwood Software, I'm not affiliated blah) and fed the infamous source.txt (the actual SSDS source code) through it.
Here's a summary...
Lines: 10,210
Statements: 7,202
Percent Comments: 45.7
Percent Branch Statements : 28.1
Subroutines: 10
Name of Biggest Subroutine: text2_Chg()
Statements in Biggest Subroutine: 6,615
Maximum Block Depth: 6
Average Block Depth: 1.44
A few additional details:
-
Of the 28.1% of branch statements, 99% are Gotos. Why use Gosubs when you have so few subroutines? I say just jam it.
-
Most of the comments are commented lines of old code, not actual comments. You never know, "If SSSS6=aa Then ok=SSSS6" might come in handy one of these days. Better keep it around just in case.
-
For you foreigners with your weird Culture.DecimalPoints and Culture.ThousandSeparators, yes, it's six thousand six hundred and fifteen statements in the biggest subroutine, appropriately named "text2_Chg()" in proper OOP fashion. Although "The_Big_Noodle()" would have been perhaps more self-descriptive, as there are no variables called "text2" anywhere in the code, and the method isn't hooked to any change event...