When is #include library required in C++?

by

Nothing in C++ prevents standard headers from including other standard headers. So if you include any standard header you might conceivably indirectly include all of them. However, this behaviour is totally implementation dependent, and if you need the features of a specific header you should always explicitly include it yourself.

More Related Contents:

  1. What is the difference between #include and #include “filename”?
  2. Do the parentheses after the type name make a difference with new?
  3. Is “delete this” allowed in C++?
  4. C++ #include guards
  5. Why does omission of “#include ” only sometimes cause compilation failures?
  6. Displaying the #include hierarchy for a C++ file in Visual Studio
  7. Subclass/inherit standard containers?
  8. Include header files using command line option?
  9. How to initialise memory with new operator in C++?
  10. Headers Including Each Other in C++
  11. placement new and delete
  12. Why isn’t `int pow(int base, int exponent)` in the standard C++ libraries?
  13. Construct path for #include directive with macro
  14. C/C++, can you #include a file into a string literal? [duplicate]
  15. Can the C preprocessor be used to tell if a file exists?
  16. How to define several include path in Makefile
  17. Difference between using #include and #include in C++
  18. Include all files in a directory?
  19. How to handle key press events in C++
  20. How can I avoid including class implementation files?
  21. What does “new int(100)” do?
  22. Does std::mt19937 require warmup?
  23. Must new always be followed by delete? [duplicate]
  24. Do I have to use #include beside ?
  25. Call destructor and then constructor (resetting an object)
  26. Will new operator return NULL? [duplicate]
  27. Why doesn’t delete destroy anything?
  28. Function already defined error in C++
  29. #include absolute path syntax in c/c++
  30. int *array = new int[n]; what is this function actually doing?

Leave a Comment