Boost C++ Libraries: Ticket #9474: boost/type_traits/has_new_operator.hpp causes compilation errors when macro "new" is defined

attachment set

anonymous — Thu, 05 Dec 2013 15:31:41 GMT

attachment → has_new_operator.hpp.patch

Steven Watanabe — Thu, 05 Dec 2013 20:59:30 GMT

Recommended by who? You should never #define keywords.

myasnikovmaksim@… — Thu, 05 Dec 2013 22:15:52 GMT

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

viboes — Fri, 06 Dec 2013 21:30:52 GMT

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

status changed; resolution set

John Maddock — Mon, 21 Apr 2014 08:40:44 GMT

status new → closed
resolution → fixed

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

myasnikovmaksim@… — Mon, 05 May 2014 17:13:56 GMT

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.

attachment set

anonymous — Tue, 20 May 2014 06:35:50 GMT

attachment → has_new_operator.hpp

attachment set

myasnikovmaksim@… — Fri, 10 Jul 2015 23:10:39 GMT

attachment → has_new_operator.hpp.2.patch

#undef BOOST_TT_AUX_MACRO_NEW_DEFINED