header-files

Personally, I quite like header-only libraries, but there are claims they cause code bloat due to over-inlining (as well as the other obvious problem of longer compile times). I was wondering, how much truth is there to these claims (the one about bloat)? Furthermore, are the costs 'justified'? (Obviously there are unavoidable cases such as when it's a library implemented purely or mostly with templates, however I'm more interested in the case where there's actually a choice available.) I know there's no hard and fast rule, guideline, etc as far as stuff like this goes, but I'm just trying to

Someone once hinted that doing this in a header file is not advised: using namespace std; Why is it not advised? Could it cause linker errors like this: (linewrapped for convenience) error LNK2005: "public: __thiscall std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >:: ~basic_string<char,struct std::char_traits<char>,class std::allocator<char> > (void)" (??1?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QAE@XZ) already defined in tools.lib(Exception.obj) Because it forces anyone who uses your header file to bring the std namespace into global scope

I am aware that definitions of C++ templated functions have to be placed in header files. However, for reasons of improved readability and structure of a (potentially) big library I am making, I separated the declarations from the implementations, into "mock" headers (which #include the implementation files, quite like this structure of files). Note that am I am aware that the implementation of templated functions must be included at compile time, and I am doing that . In short, I have a "multiple definition" error when I add a non-templated function declaration into the implementation file .

I'm using Dev-CPP, (but programming in C), and the header files won't work. I've gone to compiler option; directories; c inludes and checked the directory is correct, and it is. The include files are stored in C:\Dev-Cpp\include and that's where it's set to receive them. For example: #include <conio.h> int main(int argc, char *argv[]) { textcolor(1); printf("Why won't header files work? \n"); system("PAUSE"); return 0; } I've tried with several other header files, but they also don't work. I'm sure the answer is really obvious, but I'm clearly too stupid to fix this. I'm also using MinGW as

I have a header file called stdafx.h and this one is precompiled of course. I've read that I should include these files into my .cpp files, but some of these statements are already needed in the header file coming with that. Should I add the stdafx into my header or into my cpp? I thought it was good practise to put it into the header, but I seem to be obliged to put it into the header instead. Example: stdafx contains freeglut. my class header file has an attribute of GLenum. Should I include the stdafx into the .h of the class? stdafx.h should be the first include in EVERY cpp file in your

I'm trying to experiment with using the JNI and JDK 9. I have a class NativeTest.java that looks like this: public class NativeTest { static { System.loadLibrary("hello"); } private native void sayHello(); public static void main(String[] args) { new NativeTest().sayHello(); } } I compile the class, then use javah NativeTest to generate the header file. Upon issuing javah , I get this warning: Warning: The javah tool is planned to be removed in the next major JDK release. The tool has been superseded by the '-h' option added to javac in JDK 8. Users are recommended to migrate to using the