Subject: Re: [boost] [mpl] Abandoning old compilers
From: Robert Ramey (ramey_at_[hidden])
Date: 2015-02-28 17:50:20
Peter Dimov-2 wrote
> Edward Diener wrote:
> We should drop VC++6/7, bcc32, dmc, old sun support from MPL to make it
> maintainable - provided that it is going to be maintained at all, or
Wouldn't be best just to leave this question to the person who actually
takes responsibility for doing the maintenance? In practical terms, the
best usage of one's time is to address that stuff that's broken and leave
the other stuff alone. Supporting compilers over a certain vintage
shouldn't be a requirement, but neither should it be a requirement that a
library NOT support an older compiler or that it be (re) implemented using
some newer version. The operative principle is
a) that it respect the current/traditional interface unless there is a good
reason to break it.
b) that it work with some defined set of recent compilers.
The rest is up to the person responsible for the library.
What I don't want to see implemented is the concept of "drive-by"
maintenance whereby someone makes a "fix" and moves on. There has to be
some particular person who takes responsibility for consistency and
-- View this message in context: http://boost.2283326.n4.nabble.com/mpl-multiset-tp4672187p4672592.html Sent from the Boost - Dev mailing list archive at Nabble.com.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk