On Thu, Mar 5, 2015 at 1:17 AM, Robert Ramey <ramey@rrsd.com> wrote:
I've been looking at another thread which address the problems of maintaining and/or finding a maintainer for MPL. I've come up with an idea for a proposal which I've laid out here: Library Idea MPL lite or MPL2 <http://rrsd.com/blincubator.com/bi_suggestion/mpl-lite-or-mpl2/>
This sounds very similar to the MPL and MPL.Core separation [1]. I didn't drop workarounds for old compilers (except for one for Borland), but MPL.Core seems to be close to what you list as MPL lite. I think it is quite possible to drop the compatibility cruft from MPL.Core, although I'm not sure how useful that would be. Others have stated that newer language features can be used but require a reimplementation. That's probably true, although I'm quite happy with the current MPL.Core interface (note - not the iterators stuff, which is not part of MPL.Core). [1] https://github.com/lastique/mpl/tree/modularization