[TR1] Time to remove TR1?
We had a discussion months ago that came to the conclusion we should remove TR1. Do we have a volunteer to do the actual removal? --Beman
Date: Tue, 17 Mar 2015 17:40:20 -0400 From: bdawes@acm.org To: boost@lists.boost.org Subject: [boost] [TR1] Time to remove TR1?
We had a discussion months ago that came to the conclusion we should remove TR1.
Do we have a volunteer to do the actual removal?
What would be required? I guess I missed the discussion.
Ahmed Charles wrote:
Date: Tue, 17 Mar 2015 17:40:20 -0400 From: bdawes@acm.org To: boost@lists.boost.org Subject: [boost] [TR1] Time to remove TR1?
We had a discussion months ago that came to the conclusion we should remove TR1.
Do we have a volunteer to do the actual removal?
What would be required? I guess I missed the discussion.
You could start by checking what of http://thread.gmane.org/gmane.comp.lib.boost.devel/254448/focus=254581 has been done already (ie, check the code). Thanks, Steve.
On Mar 18, 2015, at 7:44 PM, Stephen Kelly
wrote: Ahmed Charles wrote:
Date: Tue, 17 Mar 2015 17:40:20 -0400 From: bdawes@acm.org To: boost@lists.boost.org Subject: [boost] [TR1] Time to remove TR1?
We had a discussion months ago that came to the conclusion we should remove TR1.
Do we have a volunteer to do the actual removal?
What would be required? I guess I missed the discussion.
You could start by checking what of
http://thread.gmane.org/gmane.comp.lib.boost.devel/254448/focus=254581
has been done already (ie, check the code).
Thanks!
We had a discussion months ago that came to the conclusion we should remove TR1.
Do we have a volunteer to do the actual removal?
No idea how that is actually done, but the current sticking point is boost.algorithm which is still using TR1 in master (ie there are unmerged changes in develop) : https://github.com/boostorg/algorithm/blob/master/include/boost/algorithm/se... John.
On Wed, Mar 18, 2015 at 11:09 AM, John Maddock
We had a discussion months ago that came to the conclusion we should
remove TR1.
Do we have a volunteer to do the actual removal?
No idea how that is actually done, but the current sticking point is boost.algorithm which is still using TR1 in master (ie there are unmerged changes in develop) : https://github.com/boostorg/ algorithm/blob/master/include/boost/algorithm/searching/ detail/bm_traits.hpp
If that’s the only problem, I can fix that. — Marshall
No idea how that is actually done, but the current sticking point is boost.algorithm which is still using TR1 in master (ie there are unmerged changes in develop) : https://github.com/boostorg/ algorithm/blob/master/include/boost/algorithm/searching/ detail/bm_traits.hpp
If that’s the only problem, I can fix that.
Thanks Marshall that would be great. Note that actually removing the lib requires some careful cooperation between Config and TR1 - the former needs to change, but only when we actually remove TR1. Suggest we do the actual removal after the release so we can do master and develop branches in one go? John.
On Wed, Mar 18, 2015 at 11:56 AM, John Maddock
No idea how that is actually done, but the current sticking point is
boost.algorithm which is still using TR1 in master (ie there are unmerged changes in develop) : https://github.com/boostorg/ algorithm/blob/master/include/boost/algorithm/searching/ detail/bm_traits.hpp
If that’s the only problem, I can fix that.
Thanks Marshall that would be great.
Done. — Marshall
participants (5)
-
Ahmed Charles
-
Beman Dawes
-
John Maddock
-
Marshall Clow
-
Stephen Kelly