Boost C++ Libraries: Ticket #6455: Boost foreach conflicts with Q_FOREACH and moc generation.

cc set

smr@… — Sat, 11 Feb 2012 18:10:54 GMT

cc smr@… added

status changed

Eric Niebler — Mon, 19 Mar 2012 22:07:02 GMT

status new → assigned

Thanks. It seems the fix to #6131 is doing more harm than good. It's been reverted on trunk, and will be merged to release as soon as the tests cycle. Thanks.

status changed; resolution set

Eric Niebler — Tue, 27 Mar 2012 19:28:34 GMT

status assigned → closed
resolution → fixed

(In [77591]) merge [77416] from trunk, fixes #6131, fixes #6455

bekveron@… — Tue, 20 Aug 2013 17:09:50 GMT

I'm having the same problem with boost 1.54.0 and Qt. Thought the issue has been fixed. So the libs are still incompatible? Do you recommend to use this workaround with QT_NO_KEYWORDS?

alex@… — Wed, 23 Jul 2014 09:38:53 GMT

Hi,

I'm still having issues with <boost/foreach.hpp> and Qt's foreach with various recent versions of boost (checked that the issue is present in 1.50.0 and 1.55.0). I will attach a single-file test case which demonstrates the issue where the application fails to compile with the BOOST_FOREACH construct present in a Qt application. The number and order of include files appears to be key, if you cut it down to just the core application and the <boost/foreach.hpp> include then the error is gone, so there's some interplay going on here. I'll also attach the errors I get when compiling on this platform (OSX 10.9 against boost 1.55.0, clang x86_64).

attachment set

alex@… — Wed, 23 Jul 2014 09:41:32 GMT

attachment → boost_foreach_qt_error_example.cpp

A test case for boost foreach's interplay with qt's foreach keyword

attachment set

alex@… — Wed, 23 Jul 2014 09:42:14 GMT

attachment → boost_foreach_error_output.txt

Error output for the attached testcase for OSX 10.9 against boost 1.55.0

alex@… — Wed, 23 Jul 2014 09:45:48 GMT

Oh my word that's so embarrassing, I had the wrong tab open in the build preferences, I am getting an error as the output shows, but my test-case still isn't working to show it. I'll work on getting it right and come back to you. If an admin wants to clean this up feel free.