Menu
I always placed my #include after the #ifdef/#define Include-Guard. Now the refactor mechanism of my IDE (Qt Creator) put it before the Include-Guard e.g.
#include "AnotherHeader.h"
#ifndef MYHEADER_H
#define MYHEADER_H
Can this cause any problems or can I leave it this way?
779
1 : one that is of or relating to American. 2 : one skilled in or specializing in phonetician. -an. adjective suffix. variants: or -ian or less commonly -ean.
'A' and 'an' are both indefinite articles used before nouns or before adjectives that modify nouns. To determine if you should use 'a' or 'an' before a word, you need to listen to the sound the word begins with. Use 'a' if the word begins with a consonant sound and use 'an' if the word begins with a vowel sound.
A noun is a word for a person, place, thing, or idea. Nouns are often used with an article (the, a, an), but not always. Proper nouns always start with a capital letter; common nouns do not.
Conjunction. A conjunction (also called a connective) is a word such as and, because, but, for, if, or, and when. Conjunctions are used to connect phrases, clauses, and sentences. The two main kinds are known as coordinating conjunctions and subordinating conjunctions.
Although less common, I believe this is considered to be acceptable, however beware: if you have circular #include's, your includes will typically include each other forever (until the pre-parser complains about the maximum include depth being reached). This will not happen with the #include's after the include guards.
(Circular #include's is not considered good style in any case, but if it is used nevertheless, it might work with #include's after the include guards, but certainly won't with the #include's before them.)
63
Simply check out, what will happen. Let's assume, that two different headers uses MyHeader.h.
AnotherHeader.h is included unconditionallyThe next time:
AnotherHeader.h is included unconditionally againIf AnotherHeader.h is include-guarded, nothing bad should happen. But generally I'd put the include-guard at the top of your file - there's no point in loading AnotherHeader.h again, when it was already loaded once.
22
If the header in question has include guards itself, you won't run into problems. Putting it inside the include guards may still speed up compilation. Something the compiler does not see takes less time to compile, even if it does not produce any errors.
27
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
