C++11 good practices: constexpr instead of #define

[duckie]

No API breakage here, juste replacing some pre-processor macros by C++11 constant expressions.

If constexpr is a problem for people using vs2013 prior to the November CTP, then a simple const would do the job.

[ChrisJefferson]

why not use int, as (a) that is the old type, and (b) you are casting to int anyway!

[duckie]

Unfortunately, this is not correct.

The parser compares this value to signed integers and the allocator to unsigned integers.

When you use a macro, it is not an int ! It is a integer literal which behavior depends on how you use it in the code. This demonstrates why macros are bad practices.

If you use an int, you have to cast to unsigned int in the allocator. If you use an unsigned int, you would have to cast it to an int in the parser.