C + + using namespace STD usage in-depth analysis

The following is a detailed analysis of the use of the using namespace Std in C + +, the need for friends can come to refer to the next

One:
<iostream> and <iostream.h> are not the same, the former has no suffix, in fact, in your compiler include folder you can see that the two are two files, open the file will find that, The code inside is not the same.

The C + + standard for the header file suffix. h has been explicitly raised and not supported, the earlier implementation defined the standard library functionality in the global space, declared in the header file with the. h suffix, the C + + standard to distinguish it from C, and in order to use the namespace correctly, it is stipulated that the header file does not use a suffix. h.

Therefore, when using <iostream.h>, the equivalent of calling the library function in C, using the global namespace, that is, the early C + + implementation;

When using <iostream>, the header file does not define a global namespace and must use the namespace Std to properly use cout.

Two:
the so-called namespace refers to the various visible ranges of identifiers.

All identifiers in the C + + standard library are defined in a namespace called Std.

Because of the concept of namespace, you can have three choices when using any identifier of the C + + standard library:

1, directly specify the identifier. such as Std::ostream rather than ostream. The complete statement is as follows:
std::cout << std::hex << 3.4 << Std::endl;

2. Use the Using keyword.
using Std::cout;
Using Std::endl;

The above procedure can be written
cout << std::hex << 3.4 << Endl;

3, the most convenient is to use using namespace std;

For example:
#include <iostream>
#include <sstream>
#include <string>
using namespace Std;

All identifiers defined within the namespace Std are valid (exposed). As if they were declared as global variables. So the above statements can be written as follows:
cout << hex << 3.4 << Endl;
because the standard library is very large, the programmer in the selection of the name of the class or function is likely to be the same name in the standard library. So in order to avoid the name conflict caused by this situation, everything in the standard library is placed in the STD of the name space. But this poses a new problem. Countless original C + + code relies on the functionality in the pseudo standard library that has been in use for many years, and they are all under global space.

So there are headers such as <iostream.h> and <iostream>, one for compatibility with previous C + + code, and one for supporting new standards.

The namespace std encapsulates the name of the standard library, which distinguishes it from the previous header file and generally does not add ". h" to the code.