Why does everybody use unanchored namespace declarations (i.e. std:: not ::std::)?

by

So, why do people always say std::
instead of ::std::

Probably because they never really had problems with ambiguity because of it.

Along the same lines: I never had to include “earth” in my address, and I’m not going to.

You have to draw the line somewhere, and this it is a reasonable assumption that others won’t make their own std namespaces, or at least that a library that does won’t be very popular. 🙂

More Related Contents:

  1. Accessing members in same namespace in C++ [closed]
  2. Why is “using namespace std;” considered bad practice?
  3. “using namespace” in c++ headers [duplicate]
  4. Using std Namespace
  5. Namespace + functions versus static methods on a class
  6. Why are unnamed namespaces used and what are their benefits?
  7. How to properly overload the
  8. printf with std::string?
  9. What are inline namespaces for?
  10. using namespace std; in a header file
  11. Namespaces in C
  12. Global scope vs global namespace
  13. Is it a good idea to wrap an #include in a namespace block?
  14. Why an unnamed namespace is a “superior” alternative to static? [duplicate]
  15. Why is my log in the std namespace?
  16. How to forward declare a class which is in a namespace
  17. Adding types to the std namespace
  18. How can I “unuse” a namespace?
  19. C++ namespaces advice
  20. Uses for anonymous namespaces in header files
  21. Why can’t I forward-declare a class in a namespace using double colons?
  22. error C2065: ‘cout’ : undeclared identifier
  23. Why can’t we declare a namespace within a class?
  24. Why and how should I use namespaces in C++?
  25. Interesting behavior of compiler with namespaces
  26. :: without a namespace
  27. Why does C++ parameter scope affect function lookup within 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