#Overflow h code#

Except containing ' ' characters and depending on if it is to be included by it is not allowed to contain a >. So as we can extract from this part, the header file name may be anything that is valid in the source code, too. The C++ documentation (I'm actually taking reference from the version N3690) defines that a header has to conform to the following syntax:Īny member of the source character set except new-line and >Īny member of the source character set except new-line and ' hpp even occurs in their language documentations about C++.īut I'm now aiming for an approvable reason WHY either way is ok, and especially why it's not subject of the language it self.

Since the ISO/IEC documents use this notation of header files and no string matching to. h if there is actually no reason against it. Introductory, as also in the previous named comments stated, my opinion is C++ header extensions are proposed to be. So as many already answered: either way is fine.įollowed by emphasizes of their own impressions. I'm answering this as an reminder, to give point to my comment(s) on 'user1949346' answer to this same OP. Identifies it as C++ header file, and works well in actual practice. Using no extension communicates nothing and forces inspection The '.h' extension is used for C headerįiles, and therefore communicates the wrong thing about C++ headerįiles. hpp for C++ a good example would be the boost library.įile extensions communicate the 'type' of the file, both to humansĪnd to computer programs. hpp extensions to indicate that they do not have corresponding. If your project is a C++ only project that makes heavy use of templates, this convention will be useful.Ĭertain template libraries that adhere to this convention provide headers with.

Hence, if they are not defined in header files, their definitions will not be resolved at link time from other compilation units.

#Overflow h code#

Such definitions in headers are useful in case of templates, since the compiler generates the code for each type only on template instantiation. hpp files are used when the prototypes are defined in the header itself. hpp header enclosing it with the extern 'C' declaration.ĮDIT :īy one convention. Or it could be included indirectly by the corresponding.

From a C viewpoint, all the C code will be plainly visible, but the C++ code will be hidden (because it won't compile in a C compiler).

Which mean that, from a C++ viewpoint, the C-compatible code will be defined as extern 'C'.

It can included directly, being protected by the _cplusplus macro: This header can be included by both a C source, and a C++ source, directly or indirectly. etc.).h : C/C++ compatible or pure C Headers You won't like it, because no effort is done to make it C-friendly (too much would be lost, like function overloading, namespaces, etc. If you're in a C module, don't even try to include it. This can be important when your project is using both C and C++ modules: Like someone else explained before me, you should do it very carefully, and its starts by the 'contract' you offer through the extension. hpp because I want the user to differentiate what headers are C++ headers, and what headers are C headers.