Boost C++ Libraries: Ticket #3305: BOOST_NO_EXPLICIT_FUNCTION_TEMPLATE_ARGUMENTS should be defined for gcc 3.4.x

attachment set

Christopher Schmidt — Thu, 30 Jul 2009 16:23:09 GMT

attachment → test.cpp

testcase

status changed

John Maddock — Thu, 30 Jul 2009 17:34:26 GMT

status new → assigned

I'm not sure if that is *exactly* the use case that that macro was intended for - is there a specific use case within Boost that requires this? I'm asking because I'd rather not disable features (or whole libraries in the case of Boost.Units) for gcc-3.4 unless we really have to.

Thanks, John.

Christopher Schmidt — Thu, 30 Jul 2009 17:51:25 GMT

I need a macro that describes that defect for my work on Boost.Fusion. At the moment, this problem is workarounded by the general use of boost::lazy_disable_if (e.g. https://svn.boost.org/trac/boost/browser/trunk/boost/fusion/sequence/intrinsic/at.hpp#L70). Of course I can still live with a general lazy_disable_if, but unfortunately this is not fast in terms of compile time and neither looks nor feels right.

cc set

Christopher Schmidt — Thu, 30 Jul 2009 18:00:22 GMT

cc Christopher Schmidt added

John Maddock — Fri, 31 Jul 2009 16:13:47 GMT

The thing is if we change this, then it'll make Boost::Units unusable on cygwin (and maybe other libraries too).

Can you not use something like:

#if defined(BOOST_NO_EXPLICIT_FUNCTION_TEMPLATE_ARGUMENTS)

BOOST_WORKAROUND(GNUC, <4)

workaround here #else conforming code #endif

status changed; resolution set

Christopher Schmidt — Fri, 31 Jul 2009 23:11:15 GMT

status assigned → closed
resolution → worksforme

A hardcoded BOOST_WORKAROUND looks reasonable to me. I am fine with this.