Changes between Version 5 and Version 6 of BoostEvo

Timestamp:

Jun 5, 2014, 1:34:17 PM (8 years ago)

Author:

Beman Dawes

Comment:

Add Case study from Jeff Garland

BoostEvo

@@ -27 +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.
 * 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.
- 
+
+=== Case study from Jeff Garland ===
+
+After 3 years of effort my project had finally put all (~1M sloc) of 1996 pre-standard legacy c++ to bed and started compiling most of our code in C++11 this year.  In large part, Boost was the tool that made that possible.  Because of Boost we were able to gradually move toward what would become the C++11 standard while hacking Boost code to work with our non-compliant compiler/std library…so that when we finally ported to g++4.8 and turned on c++11 it was just a handful of changes we had to make.  And now we’re successfully mixing plenty of C++11 with C++98 code in production use. 
 
 ----