Dear Open Hub Users,
We’re excited to announce that we will be moving the Open Hub Forum to
https://community.blackduck.com/s/black-duck-open-hub.
Beginning immediately, users can head over,
register,
get technical help and discuss issue pertinent to the Open Hub. Registered users can also subscribe to Open Hub announcements here.
On May 1, 2020, we will be freezing https://www.openhub.net/forums and users will not be able to create new discussions. If you have any questions and concerns, please email us at
[email protected]
http://www.ohloh.com/projects/3773
2,223,455 LOC.. Eh? I don't think so.
I checked the LOC by hand on a local enlistment, and the LOC is correct. I suspect you've added much more code to the Ohloh project page than you intended.
The source code URL entered for this project was http://svn1.cvsdude.com/saladyears/Cities3D/trunk, which includes the compete source code and documentation for a lot of third party libraries: boost, wxWidgets, fmod, etc. I know that boost alone has over one million lines of code.
If you want to see just the contents of the Cities3D directory, you can undo this source code enlistment and replace it with a link to http://svn1.cvsdude.com/saladyears/Cities3D/trunk/Cities3D.
A related but opposite query
I count 14481 LOC for:
http://fslint.googlecode.com/svn/trunk
But you estimate 53 ?
http://ohloh.net/projects/3967
cheers,
P�draig.
Hi pixelbeat,
I took a look through our analysis for this project. It looks like we simply don't recognize the language this project is written in. Off the top of my head, I don't even know what language the *.po
file extension is used for -- which goes a long way toward explaining why our system doesn't know. :-)
Our system is also very dependent on file extensions for language identification, and it gets pretty lost when a file doesn't have any extension at all. In your case, this means we are not recognizing very many of your bash scripts. This is an issue that a lot of people are pushing us to fix.
Thanks,
Robin
po files are national language translation source files, and are very common.
You could use the logic in file to identify source?
$ file fslint-gui fslint/findup
fslint-gui: a python script text executable
fslint/findup: Bourne-Again shell script text executable
cheers,
P�draig.
Hi pixelbeat,
Thanks so much for your feedback - you're helping us improve. I added some logic to do a better detect script files. I re-analyzed fslint and now come up with 2,260 physical LOCs. While this is better than our previous number (...53? that was ridiculous!), it's nowhere near your estimate of 14,481. Could you please educate me about how you came up with that number? Thanks again!