20,741
edits
Deboosting FlightGear: Difference between revisions
m
→Status: https://sourceforge.net/p/flightgear/mailman/message/36984349/
m (→Status: https://sourceforge.net/p/flightgear/mailman/message/36984349/) |
|||
| Line 19: | Line 19: | ||
dependency, but understand it is here to stay for the health of LTS | dependency, but understand it is here to stay for the health of LTS | ||
releases that use it.<ref>https://sourceforge.net/p/flightgear/mailman/message/37022287/</ref> | releases that use it.<ref>https://sourceforge.net/p/flightgear/mailman/message/37022287/</ref> | ||
looking at the boost for-each changes, wondering how simple the | |||
change was going to be. When I looked again there was just one left. Did | |||
you miss sgTileDetailsCallback.hxx, or did you leave it as an exercise for | |||
the student? | |||
<code>#include <boost></code> is down to 108 cases in 65 files.<ref>https://sourceforge.net/p/flightgear/mailman/message/36984285/</ref> | |||
{| class="wikitable" | |||
|- | |||
! Feature !! Status !! Comments | |||
|- | |||
| <code>BOOST_FOREACH</code> || {{Pending}} || The only BOOST_FOREACH left is because the case is a little bit special: | |||
the 'bin' variable is declared outside of the loop. So, it can not be | |||
replace by a C++ 11 for range loop.<ref>https://sourceforge.net/p/flightgear/mailman/message/36984349/</ref> | |||
|- | |||
| tuple & tuple_comparison || {{Pending}} || 14 found in 10 files | |||
|- | |||
| core/enable_if & utility/enable_if || {{Pending}} || 7 cases in 3 files (there are additional | |||
files that already use std::enable_if) | |||
|} | |||
== Background == | == Background == | ||