Boost C++ Libraries: Ticket #8120: DONT_USE_HAS_NEW_OPERATOR warning with MSVC and Intel compiler

Robert Ramey — Mon, 25 Feb 2013 19:40:10 GMT

Hmmm that might be a big issue. I believe that defined(..) is used through out the code since it was more robust than checking a value. It never occurred to me that it wasn't supported by the standard. Maybe we should file an report to the standard.

How many instances of "defined(...)" did you have to change?

Robert Ramey

Steven Watanabe — Tue, 26 Feb 2013 15:02:17 GMT

defined(...) only works at the top level inside #ifdefs. "If the token defined is generated as a result of this replacement process ... the behavior is undefined" (C++11 16.2) However, using XXX != 0 will also generate warnings. I believe that BOOST_WORKAROUND is safe to use.

status changed; resolution set

Robert Ramey — Mon, 03 Feb 2014 22:52:54 GMT

status new → closed
resolution → fixed

I've removed this macro so I think this is no longer an issue

status, version changed; resolution deleted

andre@… — Sun, 30 Aug 2015 11:13:16 GMT

status closed → reopened
version Boost 1.49.0 → Boost 1.59.0
resolution fixed

Hello

The issue is still there with boost 1.59 In line 60 of boost\archive\detail\iserializer.hpp there is still the code:

#define DONT_USE_HAS_NEW_OPERATOR (                    \
       BOOST_WORKAROUND(__IBMCPP__, < 1210)            \
    || defined(__SUNPRO_CC) && (__SUNPRO_CC < 0x590)   \
)

And the Intel Compiler 15.0 together with Visual Studio 2015 produces the warning: .\boost/archive/detail/iserializer.hpp(64): warning #3199: "defined" is always false in a macro expansion in Microsoft mode So from my point of view the "bug" has not been fixed and this thread does not contain a workaround for fixing it. That's why I reopened this ticket.

Best regards

status changed; resolution set

Robert Ramey — Mon, 28 Sep 2015 05:31:29 GMT

status reopened → closed
resolution → invalid

This produces a warning for microsoft and intel in microsoft mode.

The warning is of no value and can be safely ignored. Eliminating this code break code for ibm and sunpro compilers. If ths really bugs you, you can submit a patch which eliminates the bogus warning without breaking code for other compilers.

status changed; resolution deleted

Mon, 28 Sep 2015 08:20:24 GMT

status closed → reopened
resolution invalid

Hello

From my point of view it is still a bug. MSVC thinks this code is wrong or at least suspicious, that why it throws this warning. From the warning text and also from the context of this code, it is not clear to me if the preprocessor really does the right thing here.

Well, you said the warning can be ignored, because the preprocessor will do everything right. That's ok... so the warning it not an impediment for users, that do not treat warning as errors. However the code is still not correct for MSVC and should be fixed in any further release.

I clearly understand, that fixing the code might be risky and could not be done very fast. That's why I think you should give a low priority to it, but you should not forget it or just close your eyes and hope there will never be an error due to that.

Best regards

Robert Ramey — Mon, 28 Sep 2015 21:55:11 GMT

I'm trying the following instead. I can't test it, so you should. Let me know how this works

#ifndef BOOST_MSVC
    #define DONT_USE_HAS_NEW_OPERATOR (                    \
           BOOST_WORKAROUND(__IBMCPP__, < 1210)            \
        || defined(__SUNPRO_CC) && (__SUNPRO_CC < 0x590)   \
    )
#else
    #define DONT_USE_HAS_NEW_OPERATOR 0
#endif

Tue, 29 Sep 2015 12:54:21 GMT

With this fix the warning is not there anymore. Tested with Intel 16.0 and MSVC2015 compiler.

Thanks :-)

status changed; resolution set

Robert Ramey — Tue, 29 Sep 2015 20:14:23 GMT

status reopened → closed
resolution → fixed