On Nov 7, 2008, at 3:53 PM, Doug Gregor wrote:
On Fri, Nov 7, 2008 at 11:55 AM, Michael Jackson
<[EMAIL PROTECTED]> wrote:
Any ideas on what we would like to keep "un-modularized" for now?
Looking
at the dependency
graph here are my own thoughts on which libraries should probably
be kept
un-modularized for now:
mpl
functional
integer
detail
utility
exception
function
preprocessor
concept_check
concept
config
type_traits
static_assert
iterator
tuple
smart_ptr
Most of these look like they belong in the core. "detail" isn't a
library. I bet "function", "iterator", "tuple", and "smart_ptr" could
be pulled out and made into modular libraries, since they shouldn't
have all *that* many dependencies.
- Doug
Did we want to proceed with this refactoring? And if so did we want to
actually move the "core" stuff into BOOST_ROOT/libs/core or just leave
it in BOOST_ROOT/boost?
Mike
_______________________________________________
Boost-cmake mailing list
Boost-cmake@lists.boost.org
http://lists.boost.org/mailman/listinfo.cgi/boost-cmake
