http://mschnlnine.vo.llnwd.net/d1/Dev/App_Themes/C9/images/feedimage.png http://channel9.msdn.com/Forums Channel 9 keeps you up to date with the latest news and behind the scenes info from Microsoft that developers love to keep up with. From LINQ to SilverLight – Watch videos and hear about all the cool technologies coming and the people behind them. http://channel9.msdn.com/Forums en Thu, 20 Jun 2013 11:00:00 GMT Thu, 20 Jun 2013 11:00:00 GMT Rev9 3 -3 -1 Okay, so if I use using namespace std;, does that mean the program will compile everything named under namespace std? Many people recommend not to make the namespace std global, but some say it doesn't matter. But I usually do the second way, typing explicitly using::string, using::cout......until I read the newly released book from Andrei Alexandrescu (highly repected person in the field), the book named C++ coding standard. (ISBN: 0-321-11358-6)

Here is a quote from the book:
But here's the common trap: Many people think that using declarations issued at namespace level (for example, using N::Widge) are safe. They are not. They are at least as dangerous, and in a subtler and more insidious way.

After reading this, I was thinking, am I doing the right way? So I thought I would ask people here how they are doing it.


// Implementation file
#include <iostream>
using namespace std;

int main()
{
// code
return 0;
}


or should I do this:


// Implemenation file
#include <iostream>
using::cout;
using::cin;
using::endl;

int main()
{
//code

return 0;
}


]]> http://channel9.msdn.com/Forums/TechOff/26983-Should-I-make-namespace-std-global/26983#26983 Fri, 05 Nov 2004 07:17:28 GMT http://channel9.msdn.com/Forums/TechOff/26983-Should-I-make-namespace-std-global/26983#26983 TheProgrammer 3 http://channel9.msdn.com/Niners/TheProgrammer/Discussions/RSS I usually do a "using namespace std" in source files (unless they are really small) and std::* in header files.  It doesn't compile anything extra, just makes your life easier.  The only way it can be bad is if you have custom classes with the same names as the STL classes, in which case you will have to fully use std::* to declare one.

]]> http://channel9.msdn.com/Forums/TechOff/26983-Should-I-make-namespace-std-global/b018f05ba297484f88c29dea0115f91e#b018f05ba297484f88c29dea0115f91e Fri, 05 Nov 2004 12:05:16 GMT http://channel9.msdn.com/Forums/TechOff/26983-Should-I-make-namespace-std-global/b018f05ba297484f88c29dea0115f91e#b018f05ba297484f88c29dea0115f91e Cory Nelson 3 http://channel9.msdn.com/Niners/PhrostByte/Discussions/RSS I don't much care one way or the other in source files.

Never put any using declarations in header files though, since you force whomever will later use those headers to have their global namespace polluted. I'm working on an application whose source I've inherited, and there "using namespace std;" was put in the precompiled header, so either I'm stuck with it for any sourcefiles I add, or I have to change a few hundred existing source files.

]]> http://channel9.msdn.com/Forums/TechOff/26983-Should-I-make-namespace-std-global/b98dd55ed9864ab081199dea0115f94b#b98dd55ed9864ab081199dea0115f94b Sun, 07 Nov 2004 11:45:37 GMT http://channel9.msdn.com/Forums/TechOff/26983-Should-I-make-namespace-std-global/b98dd55ed9864ab081199dea0115f94b#b98dd55ed9864ab081199dea0115f94b Sven Groot 3 http://channel9.msdn.com/Niners/Sven Groot/Discussions/RSS