[Please do not mail me a copy of your followup]
boost@lists.boost.org spake the secret code
On Fri, Jan 3, 2014 at 12:31 PM, Richard
wrote: However, once a library has been accepted, it doesn't seem to go through any more peer review.
That depends on the conditions attached to acceptance by the review manager. [...]
I'm talking about after everything required by it's initial review has been completed and submitted. ...but the maintainer can still make commits to the library and do things in this subsequent phase that never would have been accepted in the original review. Things like poor or missing documentation. Things like reinventing the wheel for supporting classes that are not the main focus of the library and are provided by other boost libraries. Things like egregious overuse of macros or other coding practices that are considered poor form in modern C++. In other words, once a library has been accepted into Boost, what prevents that library from suffering from "code rot"? -- "The Direct3D Graphics Pipeline" free book http://tinyurl.com/d3d-pipeline The Computer Graphics Museum http://computergraphicsmuseum.org The Terminals Wiki http://terminals.classiccmp.org Legalize Adulthood! (my blog) http://legalizeadulthood.wordpress.com