Rob
Rob

Reputation: 78658

Adding types to the std namespace

Is it acceptable to add types to the std namespace. For example, I want a TCHAR-friendly string, so is the following acceptable?

#include <string>

namespace std
{
    typedef basic_string<TCHAR> tstring;
}

Or should I use my own namespace?

Upvotes: 19

Views: 5567

Answers (7)

jeffery
jeffery

Reputation: 129

This is an interesting question because it's completely subjective to the project and the engineers' accepted coding standards.

For a single programmer, why not... just be careful.

For teams, make a standard...

For a cross-platform project, hell yeah.

Otherwise, nawdawg.

Upvotes: 2

Johannes Schaub - litb
Johannes Schaub - litb

Reputation: 507005

Only specializations are allowed. So for example, you are allowed to specialize std::numeric_limits for your type. And this of course must happen in namespace std::. But your typedef isn't a specialization so that's causing undefined behavior.

Upvotes: 20

Lightness Races in Orbit
Lightness Races in Orbit

Reputation: 385194

[C++11: 17.6.4.2.1/1]: The behavior of a C++ program is undefined if it adds declarations or definitions to namespace std or to a namespace within namespace std unless otherwise specified. A program may add a template specialization for any standard library template to namespace std only if the declaration depends on a user-defined type and the specialization meets the standard library requirements for the original template and is not explicitly prohibited.

Upvotes: 19

Luc Touraille
Luc Touraille

Reputation: 82081

I totally agree with other answers saying that you should put your types in your own namespace to avoid unfortunate name collisions.

However, I wanted to precise that sometimes, you can (and should !) add stuff in the std namespace. This is the case for template specializations of the std::swap method for example, which are used to provide a uniform way to swap objects. For more information on this matter, you can read about the non-throwing swap idiom.

Upvotes: 2

Chris Jefferson
Chris Jefferson

Reputation: 7157

Officially, the standard says that's "undefined behaviour", and all kinds of nasty things can happen.

In practice, it will work fine, but you still shouldn't do it. What does it buy you, other than confusing people that something is provided by the compiler?

Upvotes: 2

Rob Walker
Rob Walker

Reputation: 47462

No ... part of the point of a namespace is to prevent name collisions on upgrade.

If you add things to the std namespace, then your code might break with the next release of the library if they decide to add something with the same name.

Upvotes: 18

Klaim
Klaim

Reputation: 69682

You should use your own namespace as adding code to the standard library will only confuse the users that will look online for informations about that addition.

All that is in std should be only the standard library and nothing else.

Upvotes: 3

Related Questions