Daryle Walker wrote:
On 12/20/04 8:58 PM, "Jonathan Turkanis" <technews@kangaroologic.com>
The main reason Jeff recommended that I switch to the "iostreams" directory, IIRC, was that it would be difficult to merge our documentation: either the state-savers would get lost as a small component of the iostreams library, or we would have to have an introductory page with links to both libraries.
Maybe the latter. (And don't forget that the introductory page would include the format library, which also shares "boost::io".) Eventually, the state-savers, the new iostreams, and the format libraries could all switch to Doxygen & BoostBook
Okay, the latter solution would be fine with me. How would you recommend the docs and tests be organized. One way would be to put the existing material for the iostreams library in the directory libs/io/iostreams. Also, we should probably get Jeff Garland's view on this. Jonathan