$include_dir="/home/hyper-archives/boost/include";
include("$include_dir/msg-header.inc")
?>
- Next message: Stephen Kelly: "Re: [boost] BOOST_HAS_PRAGMA_ONCE"
- Previous message: Olaf van der Spek: "Re: [boost] BOOST_HAS_PRAGMA_ONCE"
- In reply to: Robert Ramey: "Re: [boost] To split, or not to split, or something else? RE: type_traits rewrite, modularization, dependencies, etc."
- Next in thread: Ahmed Charles: "Re: [boost] To split, or not to split, or something else? RE: type_traits rewrite, modularization, dependencies, etc."
Robert Ramey wrote:
> a) make boost/serialization and boost/archive separate modules
...
> So far no one has proposed this.
I have.
I'd only move _some_ of boost/serialization into a new module and not all of
it, but the principle is generally the same. The part that you need to make
a type serializable in module A, everything else in module B.
(One could also retire pfto.hpp while one's at it, but that's a side issue.)
- Next message: Stephen Kelly: "Re: [boost] BOOST_HAS_PRAGMA_ONCE"
- Previous message: Olaf van der Spek: "Re: [boost] BOOST_HAS_PRAGMA_ONCE"
- In reply to: Robert Ramey: "Re: [boost] To split, or not to split, or something else? RE: type_traits rewrite, modularization, dependencies, etc."
- Next in thread: Ahmed Charles: "Re: [boost] To split, or not to split, or something else? RE: type_traits rewrite, modularization, dependencies, etc."
$include_dir="/home/hyper-archives/boost/include";
include("$include_dir/msg-footer.inc");
?>