"Pavel Chikulaev" <pavel.chikulaev@gmail.com> writes:
"David Abrahams" <dave@boost-consulting.com> wrote in message news:ud5pjfsi6.fsf@boost-consulting.com...
I don't know what you mean; compilable examples, maybe? And these too.
I haven't gotten around to applying my LitRe example testing and extraction system to it yet. I mean such style of familiarization with library is only for the first time, no one ever going to read it again completely, and complete code of tutorial in one place instead of scattered parts is very good when someone needs to remember all features of boost.parameter.
Of course, once we have BOOST_AUTO in the CVS, something like that could be used. That *might* be worth mentioning in the tutorial someday. OTOH, the uses of BOOST_AUTO are so broad that we'd have to sprinkle "Oh, BTW, BOOST_AUTO might be useful here" throughout the documentation of many many Boost libraries. Is it possible to add such macro now, I mean even now when we don't have boost.typeof in boost?...
No. We're in feature freeze.
no compatibility issues, Compatibility issues are discussed throughout the tutorial. That's not a good place them IMHO. Copy/Paste it.
I'll consider doing that, thanks.
and page for "might be useful" headers of other libraries... I have no clue what "might be useful," and none of our other libraries have such a page. I don't expect I'll be doing that, at least not for 1.33. The headers of other libraries you have used in your code,
How is that different from "dependencies" you requested below?
and maybe some other we still don't know about them...
That's still way too vague for me to understand what I should write or why I should write it.
And maybe dependencies... I don't think I'll be doing that either. I think bcp is the way to get that information. Ok.
-- Pavel Chikulaev
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
-- Dave Abrahams Boost Consulting www.boost-consulting.com