When? When do you need to use seperate files for one program? I've seen it in many different programs, and i'm not talking header files, i'm talking source files. Any ideas when it is appropriate? I don't understand why it'd ever be needed. oO
Seperate files for one program
Started by Phoenixz, Mar 25 2009 10:56 AM
3 replies to this topic
#1
Posted 25 March 2009 - 10:56 AM
|
|
|
#2
Posted 25 March 2009 - 01:07 PM
I was with you a while back. What happens is you will build a piece of standard functionality and you start using it in every project. You then start having to copy/paste it all over the place. So far, not a huge deal.
Then one day you find a bug in your code. Now you have to find EVERY program that has that buggy code and fix it! With separate files, you just recompile everything after making the fix in one place.
Then one day you find a bug in your code. Now you have to find EVERY program that has that buggy code and fix it! With separate files, you just recompile everything after making the fix in one place.
#3
Posted 25 March 2009 - 06:42 PM
I find it easier to let individual files represent individual objects. It makes organization (and thus debugging) a lot easier when dealing with large projects.
#4
Posted 29 March 2009 - 11:50 AM


Sign In
Create Account



Back to top









