[RESULT] [VOTE] Proposal to deprecate C++03 support as of 0.12.0

2019-01-04 Thread James E. King III
Voting has ended. Binding Votes: +1 [3: Randy Abernathy, Ben Craig, James E. King III] 0 [0] -1 [0] There were no Non-Binding Votes. The result of the vote is ***successful***. thrift-0.12.0 will be the last version of thrift that contains C++03/C++98 support. If we follow through with the w

Re: [VOTE] Proposal to deprecate C++03 support as of 0.12.0

2019-01-01 Thread Randy Abernethy
+1 On Sun, Dec 30, 2018 at 6:47 AM James E. King III wrote: > > Advantages: > > 1. Simplify the C++ runtime implementation mainly > in the areas of threading. > 2. Resolve platform porting issues. > 3. Eliminate the dependency on boost for runtime. > > Disadvantages: > > 1. Folks who

Re: [VOTE] Proposal to deprecate C++03 support as of 0.12.0

2018-12-30 Thread James E. King III
Thanks for that suggestion! Based on my experience with getting CI working on different boost repositories, I would recommend these minimums for thrift and C++11: gcc 4.8 clang 3.8 MSVC 2012 or later (although honestly, 2012 and 2013 MSVC editions can be pretty weird sometimes). - Jim On Sun, D

Re: [VOTE] Proposal to deprecate C++03 support as of 0.12.0

2018-12-30 Thread Ben Craig
+1 I'm pretty sure I'm one of the people that was opposed to this a few years ago. It's been long enough now... it's time to upgrade to 11. I recommend you pick a minimum GCC, MSVC, and Clang, and advertise support for those, rather than just say "C++11". On Sun, Dec 30, 2018 at 8:47 AM James E

[VOTE] Proposal to deprecate C++03 support as of 0.12.0

2018-12-30 Thread James E. King III
Advantages: 1. Simplify the C++ runtime implementation mainly in the areas of threading. 2. Resolve platform porting issues. 3. Eliminate the dependency on boost for runtime. Disadvantages: 1. Folks who need C++03 support are stuck at 0.12.0 Other projects like boost are beginning