CODEWITHSUNDEEP
cheaderinclude
ChrisMcJava
ChrisMcJava

Reputation: 2293

include <stdbool.h> in both the header and the source?

I am still new to C. I have a question regarding source and header files. I have a header file like this:

#ifndef MISC_H_
#define MISC_H_
#define BYTE 8

#include <stdbool.h>
#include <stdio.h>
#include "DataStruct.h"

bool S_areEqual(char *firstString, char *secondString); /* (1) */
bool S_randomDataStructureCheck(char *string, DataStruct *data); /* (2) */

#endif

  1. bool is used in the function parameters, and thus, I have it in the source as well. Do I have to #include <stdbool.h> in both the header file and the source file? Are there circumstances where I would and where I wouldn't?

  2. What if I had a typedef in another header file that was used in the header as a function parameter? Do I have to #include "DataStruct.h" in both the header file and the source file?

What is the standard?

Upvotes: 3

Views: 2885

Answers (2)

acarlon
acarlon

Reputation: 17272

No you don't have to include in both header and source (.c) file. If you have included in a header that is included by the source then it will be available to the source as well. The order of header inclusion can be important when some headers depend on others. See this answer for more detail.

As an aside, you will notice the lines

#ifndef MISC_H_
#define MISC_H_

That ensures that the header is only included once.

Update

From the comments:

so in the source, you just include its respective header?

If you mean, should a source file only include its respective header, then it depends. Generally, files should include the files that they need.

If a source file needs a header, but that header is not needed by its own header file, then the include should go in the source rather than its header. One reason is that it is just conceptually cleaner that each file includes only the files that it needs, so it is easy to tell what the dependencies are. The other reason is that it reduces the impacts of change.

Lets look at an example. Say you have foo.c and foo.h and foo.c needs foodep.h to compile, but foo.h doesn't:

Option 1: foo.h

#include "foodep.h"

Now imagine that there are a number of other files foo1.h, foo2.h, foo3.h, etc that include foo.h. Then, any change to foodep.h affects all of those other files and their dependent header and source files.

Option 2: foo.c

#include "foodep.h"

Now, no other files have visibility of foodep.h. A change to foodep.h only impacts foo.c.

Generally, try to apply the same practices as you do with Object Oriented programming - encapsulate and minimize the scope of change.

Upvotes: 3

0xF1
0xF1

Reputation: 6116

The simple way to view this is that you should always include the headers which provide functions/aliases/macros you are using in your program, whether they actually need to be included should be left to compiler.

This is because every header is defined under #ifdef - #endif clause conditioned on some header-specific MACRO (And it is necessary to do this if you define your own header, to avoid multiple inclusions and thus avoid painful compiler errors).

Thus, my advice, if you are using bool in your program, you should include stdbool.h. If the compiler has already included it in definition of some other header, it will not include stdbool again.

Upvotes: 0

Related Questions