I have a couple questions about Boost and its implications for the "physical design" of C++ projects. I'm guessing there probably aren't that many non-member, non-template functions in the Boost library, but of the ones that exist, are these usually labeled `static`, since boost is mostly a header library? Is there any advice on taming (1) the generated code size and/or (2) the build times* which result from using a header-mostly library like Boost? A large C++ project consists of many translation units (.o files) which are generated from source files that include many of the same Boost headers over and over again. (2) can be ameliorated with a distributed build process, but the more general issue here is that of consumption of compute resources, be it time or machines. -- Yang Zhang http://www.mit.edu/~y_z/