Many Header Files

I am developing an application using MSVC++ that is getting somewhat large. I make a new source and header file for each task I need to carry out. I don't know where to include all the header files. Currently, I put a header files in each source file that will call a function from it. It seems I may be repeating where and how often the header file should be included. Is there a rule / guideline? Can I have ONE header file which includes all the other header files I wrote. And that ONE header file will be included in the rest of the source files??? THANKS

Quote:

---

Originally Posted by matth

It seems I may be repeating where and how often the header file should be included.

---

Typically this is dealt with through the use of inclusion guards:

file1.h

Code:

---

#ifndef FILE1_H
#define FILE1_H

// Put your prototypes, etc. here

#endif

---

file2.h

Code:

---

#ifndef FILE2_H
#define FILE2_H

// Put your prototypes, etc. here

#endif

---

etc... for each header file.

This helps break the recursion that can sometimes develop if header file 1 includes header file 2 which includes header file 1 which includes header file 2 which includes header file 1, etc.........

Quote:

---

Originally Posted by matth

Can I have ONE header file which includes all the other header files I wrote. And that ONE header file will be included in the rest of the source files???

---

Probably, look at windows.h as an example of a single file that includes multiple files that in turn include multiple files, etc. It's debateable in my mind whether the inclusion of files behind the scenes is better or worse than a long list of inclues in a given project, but if you are including the same list of headers in project after project after project, then I believe the technique you describe is legal.

Quote:

---

Originally Posted by matth

Can I have ONE header file which includes all the other header files I wrote. And that ONE header file will be included in the rest of the source files???

---

Yes. Download the SMAUG codebase and you'll see that they do the same thing. As a matter of style, I don't like it at all. It makes it tough to see what functions are in what object files. I prefer one header per each source file.