By using this site, you agree to our Privacy Policy and our Terms of Use. Close

Forums - General - A question for all you programmers out there

For a program written solely by me, about 80,000. Though I have worked on a team that ranged in size from 20 to 100 (changed as required during lifetime of project) that had over 3 million lines of code in it. I just finished a code backup of the mainframe component and that alone consists of 473,000 lines of code.

Edit: FYI it is actually not a good bragging right to have too much code. We spend far more time tuning and removing code than we do adding code now. My effort for this week so far is the removal of 1800 lines of code  and replacing it with 100 or so lines of efficient code So a net loss of 1700



Around the Network

I've never had to keep track.



Why on Earth are you learning/using C? There is so much emphasis on OOP these days that you're essentially confining yourself to a very small, specialized area.

Personally, maybe 5,000 lines. I cannot remember. It utilized an OpenGL library for Java. Anything graphic intensive will require far more lines of code.

As others have stated, it is quite common to have to modify/enhance/fix systems with millions of lines of code in the industry.



dsgrue3 said:
Why on Earth are you learning/using C? There is so much emphasis on OOP these days that you're essentially confining yourself to a very small, specialized area.

Personally, maybe 5,000 lines. I cannot remember. It utilized an OpenGL library for Java. Anything graphic intensive will require far more lines of code.

As others have stated, it is quite common to have to modify/enhance/fix systems with millions of lines of code in the industry.


1.   You probably shouldn't judge a persons complete education from a few sentences on a videogame site thread.

2.  I know both C++ and Java which are both OOP languages.

3.  C can be used as OOP.

4.  I just applied to 3 jobs last Tuesday who all use regular C to program firmware, embedded devices, or software.



Check out my video game music blog:

http://games-and-guitars.synergize.co/

 

 PROUD MEMBER OF THE PLAYSTATION 3 : RPG FAN CLUB

 

He who hesitates is lost

dsgrue3 said:
Why on Earth are you learning/using C? There is so much emphasis on OOP these days that you're essentially confining yourself to a very small, specialized area. 


Actually, it's pretty good to start. Before learning OO it's better to know thing like memory management, pointers, implementation of data structures (stack, queue, etc). That knowledge will save him a lot of trouble in other languages.



Around the Network
torok said:

dsgrue3 said:
Why on Earth are you learning/using C? There is so much emphasis on OOP these days that you're essentially confining yourself to a very small, specialized area. 


Actually, it's pretty good to start. Before learning OO it's better to know thing like memory management, pointers, implementation of data structures (stack, queue, etc). That knowledge will save him a lot of trouble in other languages.


Thank you torok.



Check out my video game music blog:

http://games-and-guitars.synergize.co/

 

 PROUD MEMBER OF THE PLAYSTATION 3 : RPG FAN CLUB

 

He who hesitates is lost

C++ requires you to do your own memory management (garbage cleanup), has pointers, and those aforementioned data structures. No reason to learn C unless you're dealing with operating systems. Personally, I hated C. To each his own.



My work project on which I am working on my own is about 10k lines now.



Lines of code is a bad thing :P depends too much on your coding style.
I did 3,000 within 4 days once and that was pretty much the only time I checked the number of lines.
I've got some scripts with 500+ lines for various websites so those sites should easily pass 10,000



i got up to about 20k (C+) but mind you i'm not a professional so my code probably sucked. it took about 2 years to write but that was working only part time (~10hrs a week) and i was interfacing with real physical equipment in an R&D lab automating experiments. the program took about 10 hours to run by the end but did what was previously about 1 weeks worth of experiments.

btw...programing with GPIB sucks.