From: David Abrahams <dave@boost-consulting.com>
"John Calcote" <jcalcote@novell.com> writes:
For those of us interested in learning more about the language, and more about boost classes and the rationale behind the implementation - and for those of us who simply don't have the technical background to "just know" the answer at a glance, as I'm sure some of you contributors do - why not provide a simple rationale for adding a particular member function to a particular class?
Rationales are central to Boost documentation: http://www.boost.org/more/lib_guide.htm#Rationale_rationale
That said, I don't think any of us is going to try to provide rationale on a member-by-member basis.
Books and articles have been written on Boost libraries, too. Those can often bridge the gap. -- Rob Stewart stewart@sig.com Software Engineer http://www.sig.com Susquehanna International Group, LLP using std::disclaimer;