Depends on the situation -

In a header, or other distributed file: Don't pollute the global namespace with a using declaration. People probably won't like that.

In a source or implementation file: It'll all get compiled away nicely, and won't affect other parts of the project. using namespace is fine.

Or, at least, that's what I do lol -

#include "PAIN_Config.h"
#include "PAIN_FMOD.h"
#include "PAIN_GUI.h"
#include "PAIN_Log.h"
#include "PAIN_OGL.h"
#include "PAIN_SDL.h"
#include "PAIN_VFS.h"

using namespace pain::config;
using namespace pain::core;
using namespace pain::fmod;
using namespace pain::gui;
using namespace pain::log;
using namespace pain::ogl;
using namespace pain::sdl;
using namespace pain::vfs;

Bear in mind that you don't need to drag the /whole/ std namespace in - you can single out particular symbols, e.g. "using std::string".

Quote:Original post by superpig
Bear in mind that you don't need to drag the /whole/ std namespace in - you can single out particular symbols, e.g. "using std::string".

This is the approach I take. Use "using" only for objects you will need... No need to include _everything_.

Thanks all, it makes sense now. I think I will try to get used to only using the ones I need :)

Thanks all, it makes sense now. I think I will try to get used to only using the ones I need :)