On Sat, Jun 30, 2012 at 3:37 AM, Tim Blechmann <tim@klingt.org> wrote:
the boost.lockfree testsuite requires the following trivial patch, which specifies the namespace for enable_if and disable_if. i've applied a similar patch to boost.parameter some time ago [1].
as it is trivial, is it ok to commit to trunk or shall i submit it to trac that the thread/exception maintainers can apply it?
Hi,
can I know more about the problem you have found?
the general pattern seems to be something like this:
namespace boost { namespace foo { [..] enable_if [..]
}}
while the fix is:
namespace boost { namespace foo { [..] boost::enable_if [..]
}}
This doesn't seem to be the case in Boost Exception. All enable_if uses are in namespace boost, not in another nested namespace.
not sure, why enable_if is not resolved, but came across the issue before in boost.parameter, when i added boost.heap into trunk. the fix is trivial, as it just specifies the scope of enable_if ...
no idea, why i triggered this issue with both boost.heap and boost.lockfree ...
I suggest we first figure out why and then make changes. :) Emil Dotchevski Reverge Studios, Inc. http://www.revergestudios.com/reblog/index.php?n=ReCode