Changes between Version 7 and Version 8 of BoostEvo

Timestamp:

Jun 5, 2014, 2:49:22 PM (8 years ago)

Author:

Beman Dawes

Comment:

Add line between bullet items

BoostEvo

@@ -19 +19 @@
 
 * If a new C++ feature can be conditionally added (via #ifdef or a macro such as BOOST_NOEXCEPT), libraries may do so as soon as any implementation being regression tested supplies the feature. The more useful the feature is to the Boost library's users, the more strongly the library maintainer is encouraged to start conditionally using the feature.
+
 * If a new C++ feature cannot be added conditionally (for example, because it would cause breaking interface changes), maintainers may add a new version of the library that uses the new feature unconditionally, while continuing to support the old version. Maintainers may choose to seek a replacement maintainer for the old version of the library, of course. Because two versions of a library are painful to maintain and confusing to users, this approach is only encouraged when the advantages of using the new C++ feature would be of great benefit to library users. This is appropriate only when there is regression test coverage, for at least one implementation, of the new feature.
+
 * Once a C++ feature has been shipping by all major C++ implementers for several releases, Boost libraries may use the feature unconditionally and stop supporting older versions that do not provide the feature. The maintainer of each Boost library must weigh the pros and cons of dropping support for older compilers and standard libraries, and consult users to gauge the impact of such a change. Example: As of mid-2014, major compilers such as Clang, GCC, and Visual C++ have supported auto, decltype, nullptr, doubled right angle brackets, long long, rvalue references, static assert, and built-in type traits for at least three major releases, so these C++11 features are among the first a Boost library might consider using unconditionally. If conditional support or two library versions do not cause an unwanted burden, maintainers are free to continue that approach into the future.
 
@@ -25 +27 @@
 
 * Authors of new libraries are encouraged to use the approaches described above to support platforms that do not support new C++ features. However, it is ultimately the decision of the library developer which versions of C++ to support and how.
+
 * New libraries will not be rejected because they lack support for older platforms, particularly if new language or library features are integral to the library interface or design. An example would be a library that cannot provide a usable interface without use of a new C++ feature.
+
 * Boost encourages the development of new, state-of-the-art libraries. The intent is to encourage innovative user interfaces and overall library designs, and if that means requiring compiler or standard library support for new C++ features, that is acceptable.