Hi There!
I am lazy and most of the time when adding certain functions to my programs, I always have to remind myself to include a certain header.
Is there just a 'lazy' and 'customizable' way to include a bunch of headers into one header? For example:
Inside of Group.h would be...Code:#include "Group.h"
And about tons of other headers I will decide to use. Thanks for your responses if you do respond!Code:#include <iostream.h> #include <time.h> #include <cstdlib> #include <conio.h> ...
Nothing wrong with that.
When in doubt, try it =).
You can, but you shouldn't.
One of the hardest things to overcome is deciding at some later date that you want to re-use some of the code in another project, only to find that you have lots of useless dependencies which take far longer to pick apart than any time saved in keeping the code tight in the first place.
Also, you end up using things you shouldn't, just because it happens to compile. If you got an error message instead, it might prompt you to think about the interface you're about to break, rather than blindly breaking it anyway.
Not only that, if you have a useless dependency, then you'll trigger lots of useless recompilations as well, when you change a header you don't actually need (but include anyway for "convenience").
You certainly don't want to mix header files from different languages / eras, like this
#include <iostream.h> // old C++
#include <time.h> // old C
#include <cstdlib> // new C++ header for old C
#include <conio.h> // ancient DOS header
One thing you must NEVER do is put something like
using namespace std;
in a header file. Doing so breaks any code which attempts to use namespaces later on, as there is no way to undo a "using" clause.
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
Great. Thanks a whole bunch! You are right though, mixing ancient headers and modern headers isn't exactly a good idea. I never planned on adding namespace to that 'all header' but thanks for the heads up.
It would be better to know individually what headers go with what functions, just to improve that function sense sort of thing. Thanks for your help!
EDIT: lol I just got it, "God of the C" that's funny. Next thing youll know it'll be "CBiscuit".
