If a class member is always initialized with the same initial value, then you should make the initializer inline, so as to avoid duplication. If the initial value depends on the constructor, then put it in the constructor initializer list. (And never use assignment in the way you did.) Example: class Foo { bool done … Read more
Let’s start with a case that is fully defined by the C standard. If file.h contains extern int x;, it declares an identifier x to refer to some int object. This declaration is a part of each of file_1.c and file_2.c during compilation, and it is “made to refer to the same object” by linkage, … Read more
Move the struct declaration to the header: customer.h typedef struct CustomerStruct { … }
One thing that I’ve used in the past (when global variables were in vogue): var.h file: … #ifdef DEFINE_GLOBALS #define EXTERN #else #define EXTERN extern #endif EXTERN int global1; EXTERN int global2; … Then in one .c file (usually the one containing main()): #define DEFINE_GLOBALS #include “var.h” The rest of the source files just include … Read more
Reason [1] Faster compile times Not in my projects: source files (CPP) only include the headers (HPP) they need. So when I need to recompile only one CPP because of a tiny change, I have ten times the same number of files that are not recompiled. Perhaps you should break down your project in more … Read more
.h: header file, its a source file containing declarations (as opposed to .cpp, .cxx, etc. containing implementations), .lib: static library may contain code or just links to a dynamic library. Either way it’s compiled code that you link with your program. The static library is included in your .exe at link time. .dll: dynamic library. … Read more
Since I could not find any complete (in my view) duplicate for this question, I am going to write a (hopefully) authoritive and complete answer. What is One Definition Rule and why should I care A One Definition Rule, usually dubbed ODR, is a rule which states (simplified) that any entity (informal term) used in … Read more
This is the process: source header source header header \ / \ | / / \ / \ | / / PREPROCESSOR PREPROCESSOR | | V V preprocessed code preprocessed code | | COMPILER COMPILER | | V V object code object code \ / \ / \ / LINKER | V executable Preprocessing #include … Read more
A self sufficient header file is one that doesn’t depend on the context of where it is included to work correctly. If you make sure you #include or define/declare everything before you use it, you have yourself a self sufficient header. An example of a non self sufficient header might be something like this: —– … Read more
If the function is small (the chance you would change it often is low), and if the function can be put into the header without including myriads of other headers (because your function depends on them), it is perfectly valid to do so. If you declare them extern inline, then the compiler is required to … Read more