[prev in list] [next in list] [prev in thread] [next in thread] 

List:       boost
Subject:    Re: [boost] [modularization] Extract xml_archive from serialization
From:       Emil Dotchevski <emildotchevski () gmail ! com>
Date:       2014-09-22 19:42:31
Message-ID: CAN5fK5GUjrVw-4_21NnSjT5Ay3yhP37YHkfn4Uhzi1oW4yWToA () mail ! gmail ! com
[Download RAW message or body]

On Mon, Sep 22, 2014 at 12:05 PM, Vladimir Prus <vladimir@codesourcery.com>
wrote:

> Yes, it's possible in principle, and even with current serialization code,
> but it's not clear that replacing
>
>         BOOST_SERIALIZATION_NVP(data_member)
>
> with
>
>         boost::serialization::make_nvp("data_member", data_member)
>
> is net win.


For users of library A who do not need its functionality that requires a
library B, allowing them to compile A without B is a net win. Especially if
A is a major coupling point, B is relatively large, and the need to use A
is independent of the need to use B.

As well, in principle the call to serialize a data member doesn't need to
be qualified: read(ar,foo_,"foo") seems quite straight-forward.

Besides, serialization usually requires access to private data members, so
breaking this dependency by refactoring read/write code into a separate
header is not possible in general.

-- 
Emil Dotchevski
Reverge Studios, Inc.
http://www.revergestudios.com/reblog/index.php?n=ReCode

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
[prev in list] [next in list] [prev in thread] [next in thread]