iostream.h is deprecated by those compilers that provide it, iostream is part of the C++ standard. To clarify explicitly there is no mention of iostream.h at all in the current C++ standard (INCITS ISO IEC 14882 2003). Edit: As @Jerry mentioned, not only does the current standard not mention it, but no standard for C++ … Read more
The best place would be in a source file // Header file class test { const static char array[]; }; // Source file const char test::array[] = {‘1′,’2′,’3’}; You can initialize integer types in the class declaration like you tried to do; all other types have to be initialized outside the class declaration, and only … Read more
You want to include <string> and use std::string: #include <string> #include <iostream> int main() { std::string s = “a string”; std::cout << s << std::endl; } But what you really need to do is get an introductory level book. You aren’t going to learn properly any other way, certainly not scrapping for information online.
This header is likely shared between the C and C++ compiler for that vendor. Did you look what __THROW is defined as? I suspect something akin to: #ifdef __cplusplus #define __THROW throw() #else #define __THROW #endif Or for actual specifications: #ifdef __cplusplus #define __THROW(x) throw(x) #else #define __THROW(x) #endif As you can see, in a … Read more
These files are usually the input for autoconf which will generate final .h files. Here’s an example from PCRE: #define PCRE_MAJOR @PCRE_MAJOR@ #define PCRE_MINOR @PCRE_MINOR@ #define PCRE_PRERELEASE @PCRE_PRERELEASE@ #define PCRE_DATE @PCRE_DATE@ Autoconf will replace all variables (@…@) with the respective values and the result will be a .h file.
If you want to use a function in multiple source files (or rather, translation units), then you place a function declaration (i.e. a function prototype) in the header file, and the definition in one source file. Then when you build, you first compile the source files to object files, and then you link the object … Read more
In short, don’t use it; use <assert.h>. C++11 removed any formal guarantee of a “c….” header not polluting the global namespace. It was never an in-practice guarantee, and now it’s not even a formal guarantee. Hence, with C++11 there is no longer any conceivable advantage in using the “c….” header variants, while there is the … 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
You should look at the depend.make files in your binary tree. It will be in CMakeFiles/target.dir/depend.make. Try to find one of those that is missing a .h file that you think it should have. Then create a bug report for cmake or email the cmake mailing list.
No, it is not safe – it won’t pollute another namespace, but it is dangerous for other reasons: A using directive will import anything that is currently visible by the name you specify into the namespace where you use it. While your using will only be visible to users of MyNamespace, other things from “outside” … Read more