Find centralized, trusted content and collaborate around the technologies you use most.
Learn more about CollectivesStack Internal
Knowledge at work
Bring the best of human thought and AI automation together at your work.
Explore Stack InternalNo, you should not. Include guards are for headers, which are included by other files. Source files, on the other hand, should never be included by other files.
Alternatively you may consider using the (non standard, but generally accepted) extension in your header files
#pragma once No, you should not. Include guards are for headers, which are included by other files. Source files, on the other hand, should never be included by other files.
Alternatively you may consider using the (non standard, but generally accepted) extension in your header files
#pragma once No, you should not. Include guards are for headers, which are included by other files. Source files, on the other hand, should never be included by other files.
Alternatively you may consider using the (non standard, but generally accepted) extension in your header files
#pragma once No, you should not. Include guards are for headers, which are included by other files. Source files, on the other hand, should never be included by other files.
Alternatively you may consider using the (non standard, but generally accepted) extension in your header files
#pragma once