Is it a good idea to wrap an #include in a namespace block?

by

No, it’s a bad idea. With C++ declarations, it’s likely to introduce linker errors as identifiers get declared in the wrong namespace. With C declarations, it works, but it may hide clashes between identifiers in the global namespace (which you were trying to avoid, I guess) until link time; it doesn’t really put the identifiers in a namespace.

A better idea would be to put your own identifiers in a namespace and avoid defining anything but main in the global one.

More Related Contents:

  1. Difference between using #include and #include in C++
  2. “using namespace” in c++ headers [duplicate]
  3. Unnamed/anonymous namespaces vs. static functions
  4. Using std Namespace
  5. How to properly overload the
  6. printf with std::string?
  7. What are inline namespaces for?
  8. How do you properly use namespaces in C++?
  9. What are the pitfalls of ADL?
  10. using namespace std; in a header file
  11. Namespaces in C
  12. C++ Header order [closed]
  13. Why is “using namespace X;” not allowed at class/struct level?
  14. C/C++, can you #include a file into a string literal? [duplicate]
  15. scope of using declaration within a namespace
  16. Circular C++ Header Includes
  17. How to define several include path in Makefile
  18. static vs non-static variables in namespace
  19. When is #include library required in C++?
  20. Is the backslash acceptable in C and C++ #include directives?
  21. C++ namespaces advice
  22. How does #include work in C++?
  23. Uses for anonymous namespaces in header files
  24. error C2065: ‘cout’ : undeclared identifier
  25. Generate include file name in a macro
  26. Where should non-member operator overloads be placed?
  27. :: without a namespace
  28. What is the use of “using namespace std”? [duplicate]
  29. extern “C” linkage inside C++ namespace?
  30. Namespaces and Operator Overloading in C++

Leave a Comment