Subject: [boost] [modularization] Improving/splitting up detail
From: John Maddock (john_at_[hidden])
Date: 2013-11-01 15:15:17
Lets say we wanted boost/detail to depend on nothing but config, here's what
it would take:
Used by graph lib only, suggest it's moved there.
Used by multi index, statechart and flyweight, suggest move to new
Depends on smart_ptr's details only, suggest those details are moved to
Used by python and test, move to "common".
Only external dependency is boost/cstdint.hpp, either move to "common",
or else move cstdint.hpp to "config".
Move to call_traits (should be there already).
Only external dependency is boost/cstdint.hpp, suggest latter is moved
Move to compressed pair (should be there already).
Move to "predef"
File appears to be unused, and not very useful, suggest we remove it.
File appears to be unused, suggest we remove it.
Used by iterator and python, move to "common"
Move to common, or better modify the libraies using this to use the
newer type_traits equivalents.
Used by graph and range, move to "common"
Used by parameter and python, move to "common"
I suspect this may be obsolete now compiler requirements have been
bumped, but whatever it's still used by multiple libs: move to "common"
Only used by lexical_cast, move it there.
Only extern dependency is smart_ptr's details, suggest move those to
Appears to be unused, suggest we remove.
Used by graph and iterator, move to "common"
Move to compressed pair, might also be obsolete by now.
Only external dependency is smart_ptr's details, suggest those are moved
here. Or since only serialization uses this, move this file there...
Used by optional and variant, move to "common".
Depends on boost/cstdint.hpp only, suggest that belongs to config.
Everything else in detail has no dependencies other than config.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk