scope of using declaration within a namespace

by

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” will be visible to your using declaration.

So how is this dangerous when used in a header? Because it will import things that are visible at the point of the declaration, the exact behavior will depend on the order of headers you include before the declaration (There might be different things visible from boost::numeric::ublas::vector). Since you cannot really control which headers are included before your header (nor should you be! headers should be self-sufficient!), this can lead to very strange problems where your function will find one thing in one compilation unit, and another in the next.

As a rule of thumb, using declarations should only be used after all includes in a .cpp file. There’s also an item on this exact issue in the book “C++ Coding Standards” by Sutter and Alexandrescu (Item 59). Here’s a quote:

But here’s the common trap: Many people think that using declarations issued at namespace level (…) are safe. They are not. They are at least as dangerous, and in a subtler and more insidious way.

Even when it’s unlikely that the name you are using doesn’t exist anywhere else (as is probably the case here), things can get ugly: In a header, all declarations should be fully qualified. This is pain, but otherwise, strange things can happen.

Also see Migrating to Namespaces, Using-declarations and namespace aliases and Namespace Naming for examples and the problem described in-depth.

More Related Contents:

  1. “using namespace” in c++ headers [duplicate]
  2. using namespace std; in a header file
  3. Global scope vs global namespace
  4. Why is “using namespace X;” not allowed at class/struct level?
  5. Why does C++ parameter scope affect function lookup within a namespace?
  6. What is the use of “using namespace std”? [duplicate]
  7. Should I include stddef.h or cstddef for size_t
  8. Why ‘&’ reference in not required in classes in C++?
  9. Why is “using namespace std;” considered bad practice?
  10. Why have header files and .cpp files? [closed]
  11. Namespace + functions versus static methods on a class
  12. Why are unnamed namespaces used and what are their benefits?
  13. What’s the scope of inline friend functions?
  14. Difference between iostream and iostream.h
  15. C/C++ header and implementation files: How do they work?
  16. Why should I use the “using” keyword to access my base class method?
  17. Is there any way to access a local variable in outer scope in C++?
  18. Is it a good idea to wrap an #include in a namespace block?
  19. Why is my log in the std namespace?
  20. How to forward declare a class which is in a namespace
  21. How can I “unuse” a namespace?
  22. Why do un-named C++ objects destruct before the scope block ends?
  23. Which headers in the C++ standard library are guaranteed to include another header?
  24. multiple definition error c++
  25. Why can’t we declare a namespace within a class?
  26. Why and how should I use namespaces in C++?
  27. How to access variables defined and declared in one function in another function?
  28. what does `using std::swap` inside the body of a class method implementation mean?
  29. extern “C” linkage inside C++ namespace?
  30. C++ Circular Dependency in Header Files

Leave a Comment