Re: [Boost-maint] Getting involved with MPL maintenance

Subject: Re: [Boost-maint] Getting involved with MPL maintenance
From: Eric Fiselier (eric_at_[hidden])
Date: 2014-06-19 14:26:01

I'm quite familiar with Louis's MPL11 and its very cool.

I'll look at how we can start to remove some of the workarounds for
compilers that are no longer supported.
However for my first couple of patches I would like to patch more
"testable" issues just to make 100% sure
I understand what I'm doing. Cleaning up those workarounds is a huge task
and I would like to get my hands dirty first.

On Thu, Jun 19, 2014 at 1:18 AM, falcou <Joel.Falcou_at_[hidden]> wrote:

> Le 19.06.2014 05:49, Eric Fiselier a écrit :
>
>  Hello,
>>
>> I want to become involved with Boost community maintenance. I was a
>> volunteer at C++Now and was told that there was plenty of work to be done
>> on Boost.MPL.
>>
>>
> indeed
>
>
>  I have a fair amount of experience with template metaprogramming and
>> Boost.MPL. I have worked on a re-implementation of the Boost.MPL interface
>> in C++11 and in doing so have read the entire library. (found here:
>> https://github.com/efcs/elib/tree/master/elib/mp)
>>
>
>
> You may want to check Louis Dionne work on a more comprehensive C++1y
> conversion of bth MPL and Fusion.
>
>
>  Since there are a large amount of tickets open against the library, I
>> would
>> like to know if there
>> are any high priority tickets that I can focus on.
>>
>
> I once triaged them on the old track. I cna have a look again and guide
> you.
> The main issue with current MPL is the huge number of ifdef//workaround
> for silly old compiler that clutter the code.
> Depending on how the list of supported compiler have been updated lately,
> one main task may be to clean those so
> patchign other issues will become easier.
> _______________________________________________
> Unsubscribe & other changes: http://lists.boost.org/
> mailman/listinfo.cgi/boost-maint