| 26 | | * Authors of new libraries are encouraged to use the approaches described above to support platforms that do not support new C++ features. New libraries will not be rejected because they lack support for older platforms, if new language or library features are integral to the library interface or design. Indeed, Boost encourages the development of new, state-of-the-art libraries. An example would be a library that cannot provide a usable interface without use of a new C++ feature. (This guideline is admittedly vague. The intent is to encourage innovative user interfaces, and if that means very limited compiler or standard library support initially, that is acceptable.) |
| | 26 | * 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. |
| | 27 | * 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. |
| | 28 | * 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. |
| | 29 | |
