Re: [boost] [thread/exception] trivial compile fix

Subject: Re: [boost] [thread/exception] trivial compile fix
From: Vicente J. Botet Escriba (vicente.botet_at_[hidden])
Date: 2012-07-01 15:49:08

Le 01/07/12 20:00, Tim Blechmann a écrit :
>>>>> 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?
>>>>>
>>>> Maybe I'm missing something but what's the relevance to Boost Exception
>>>> here?
>>> it is a fix/workaround for boost.thread and boost.exception. all it
>>> changes is to use boost::enable_if instead of enable_if
>> Isn't better to understand why ? It's not normal that enable_if inside
>> a nested namespace needs to have boost:: specified and while we are at
>> it why boost::enable_if and not ::boost::enable_if ?
> feel free to look into it:
>
> * check out trunk
> * go to libs/lockfree/tests
> * change the files: move the inclusion of boost/test/unit_test.hpp to
>    the front of the file (or apply attached patch)
> * compile the testsuite
> * get a deeper understanding of the situation
>
> i'm not planning to dig deeper into these libraries, myself
>
>
As I said, there is already an issue reported on this ML

http://boost.2283326.n4.nabble.com/Boost-Test-g-compilation-error-due-to-ambiguity-between-template-lt-class-Cond-class-T-gt-struct-boo-tt4282786.html

Best,
Vicente