Recent Features
| |||||||||||||
Blank linesBlank linesPosted Feb 17, 2010 23:04 UTC (Wed) by xoddam (subscriber, #2322)In reply to: How old is our kernel? by nix Parent article: How old is our kernel?
The measurement is entirely relative -- LOCs ain't LOCs, except in the special case where the code is written in the same language, in the same style, even in the same codebase.
If it is a valid, apples-to-apples comparison to compare the line count without blank lines (debatable, but I think it is in this case : it's all Linux kernel code after all), I reckon it's equally valid to compare it with them.
(Log in to post comments)
Blank lines Posted Feb 18, 2010 10:16 UTC (Thu) by hummassa (subscriber, #307) [Link]
This seems to me a speculative, rather than a factual, answer.
I'd suggest cleaning all and anyy comments, blank lines and strings from the measurements, and comparing. Does not seem too difficult to do.
Blank lines Posted Feb 18, 2010 14:11 UTC (Thu) by nix (subscriber, #2304) [Link]
I'd call comment and string changes significant. The only reason I singled out blank lines is because they really *cannot* change in a meaningful manner.
Blank lines Posted Feb 19, 2010 10:33 UTC (Fri) by hummassa (subscriber, #307) [Link]
From the POV of the development process, yes, you are right.
But if you are measuring the age of the code, I would weed out anything that ends up generating the same object code. Just my opinion there.
Blank lines Posted Feb 26, 2010 8:51 UTC (Fri) by efexis (guest, #26355) [Link]
Unless the blank lines were proportionally evenly distributed, in which case the effect would simply be cancelled out, but even so... a character changed in a long line of code counts the same as the whole line changing, but it's enough to give a feel for what's going on, as long as it's understood that these types of stats serve to guide towards reality rather than define it.
|
|||||||||||||