*. h or *. hpp for your C++ headers class definitions I've always used a * h file for my class definitions, but after reading some boost library code, I realised they all use * hpp I've always had an aversion to that file extension, I think mainly be
. c vs . cc vs. . cpp vs . hpp vs . h vs . cxx - Stack Overflow Possible Duplicates: * h or * hpp for your class definitions What is the difference between cc and cpp file suffix? I used to think that it used to be that: h files are header files for C and C
#include in . h or . c . cpp? - Stack Overflow I propose to simply include an All h in the project that includes all the headers needed, and every other h file calls All h and every c cpp file only includes its own header
c++ - cstdio stdio. h namespace - Stack Overflow Including cstdio imports the symbol names in std namespace and possibly in Global namespace Including stdio h imports the symbol names in Global namespace and possibly in std namespace The same applies for all c-styled headers
c - netdb. h not linking properly - Stack Overflow Linking doesn't attach a header file to the program, pre-processing handles header files Linking attaches shared object libraries (look in usr lib) to compiled objects Sometimes it is not sufficent to just add "-lnetdb" as the library might not be in the linker path In that case, you need to use a -L (path) to add a path entry so the directive "-lnetdb" can find the correct netdb so file