"Robert Ramey" <ramey@rrsd.com> writes:
There's another point that has me a little bit stumped. Most of the boost libraries are code that one invokes with a documented signature. The list of invocations, syntax and semantics is what I think Vladimir is referring to here with "reference documentation". However, the serialization library is more "upside down" in that using it consists almost entirely of filling in stubs called by the serialization algorithm. So its not clear to me how the "reference documentation" would look compared to the current documents.
That's usually done by describing concept requirements of the parameters to the serialization algorithm. See http://www.boost.org/libs/iterator/doc/iterator_facade.html#iterator-facade-... for an example. -- Dave Abrahams Boost Consulting http://www.boost-consulting.com