boost/type_traits/has_new_operator.hpp causes compilation errors when macro "new" is defined

[myasnikovmaksim@…]

It is a recommended practice to #define new DEBUG_NEW in order to detect memory leaks in MFC projects, but it causes compilation errors in boost/type_traits/has_new_operator.hpp due to undesirable macro substitution.
I suggest to hide this macro at the beginning of the file and restore it at the end. Attached patch is suitable only for Visual C++ compiler.
Best regards, Maksim.

[Steven Watanabe]

Recommended by who? You should never #define keywords.

[myasnikovmaksim@…]

Microsoft, I guess :-)
I'm absolutely agree with about #defining keywords, but this happens.

[viboes]

Replying to myasnikovmaksim@…:

Microsoft, I guess :-)
I'm absolutely agree with about #defining keywords, but this happens.

Please don't do this. Repalce instead the global ::new/::delete operators. ​http://stackoverflow.com/questions/8186018/how-to-properly-replace-global-new-delete-operators

[John Maddock]

Fixed in Git develop, but none the less as Viboes said: "don't do that"!

[myasnikovmaksim@…]

Replying to johnmaddock:

Fixed in Git develop, but none the less as Viboes said: "don't do that"!

Thank you. Needless to say that keyword redefinition is evil, but ancient code can be tricky.
A minor adjustment if you please: there is no reason to keep macro BOOST_TT_AUX_MACRO_NEW_DEFINED defined after pop_macro("new") pragma.

[myasnikovmaksim@…]

#undef BOOST_TT_AUX_MACRO_NEW_DEFINED