On 4/24/19 9:00 AM, stefan via Boost wrote:
On 2019-04-24 11:56 a.m., Joaquin M López Muñoz via Boost wrote:
Not sure if this helps, but the way I did it in Boost.Flyweight is by isolating all serialization code in a separate header:
https://www.boost.org/libs/flyweight/doc/reference/flyweight.html#serialize_...
So, if I want to serialize boost::flyweight's, I need to include
and link with Boost.Serialization. This, I think, makes Boost.Flyweight technically not dependent on Boost.Serialization. Right, this is *exactly* what I tried to propose as the right approach in my first reply. :-)
Right - every library should be doing this. Likely the same applies to other libraries as well. Robert Ramey
Stefan
--
...ich hab' noch einen Koffer in Berlin...
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost