Forum Posts

This metric is still incorrect. I thought it was odd that I had such a large amount of C++, apparently a significant amount of my Objective-C is being counted as C++...

For assembly code, the common style is to have every line split, with a single statement followed by a comment. Code written in this way should have a comment ratio of 50% (one comment per line), but ... [More] ends up with a comment ratio of around 1% (only comments that are longer than a half-line count). [Less]

Oh, and it's also incorrectly detecting Objective-C headers as C++ in at least one case, see: https://www.ohloh.net/p/gnustep/commits/57973118 You can test the difference between an Objective-C ... [More] header and a C++ header trivially by seeing if it contains the token '@end'. I'm not sure what heuristic you are using, but it's broken. [Less]

This flaw is also skewing other statistics, such as the average comment ratio. The comment ratio in machine-generated autoconf files is, as you would expect, 0%. The comment ratio in human-edited ... [More] files is much higher, but with Ohloh counting the computer-generated autoconf files when calculating language totals this brings the total comment ratio down significantly. [Less]

Ah, I see. The configure and config.in files are both auto-generated. The actual change was one line in configure.ac. If the code metrics are counting every addition to the configure file as an ... [More] addition then that's going to be skewing the statistics quite a lot... In the latest checkout there are about 32KLOC in config*, but only about 2KLOC of these are human-edited, the rest are generated by autoconf. Ideally, Ohloh should only be counting the human-edited version in the statistics. In the same checkout, there are 175KLOC of Objective-C, so the ratio of autoconf to Objective-C is quite inaccurate, even if you are counting the machine-generated autoconf instead of the source files. [Less]

Your UI doesn't seem to let me know which commit your information is coming from and, given that I have never written any autoconf code, I can't tell you which of my commits contains autoconf code ... [More] (because none of them do). That said, you're only tracking 23 commits by me related to GNUstep, and between them they (apparently) cover 18,651 lines of autoconf stuff, so that should help you narrow it down a bit... [Less]

In fact, the autoconf numbers are total nonsense. It thinks I've changed 18,651 lines of autoconf code in a single commit for GNUstep when, in fact, I have never touched autoconf...

Thanks, now it's picked up all of the commits. The language metrics still look wrong though. It lists 48% C, 30% Objective-C, 13% Autoconf. I'd be very surprised if the code is 13% autoconf and ... [More] given that almost all of it is Objective-C I'm also surprised that it's listing C instead of Objective-C as the majority. [Less]

It's a little bit better, but now it's claiming the last commit was six months ago. Are there any other problems?

The Ohloh stats for GNUstep show that it has not been updated for over a year, while the latest svn activity was about half an hour ago (see http://cia.vc/stats/project/gnustep). The metrics also ... [More] seem wrong, for example claiming that it is mostly written in C when it is 90%+ Objective-C. User widgets also don't seem to be being updated; mine still says 576 commits while my user page says Ohloh has tracked 831 commits by me... [Less]