Re: [boost] [serialization] load-only or save-only types?

Subject: Re: [boost] [serialization] load-only or save-only types?
From: David Abrahams (dave_at_[hidden])
Date: 2008-11-03 23:39:36

on Mon Nov 03 2008, "Hartmut Kaiser" <hartmut.kaiser-AT-gmail.com> wrote:

>> I want to send out instances of one type and receive the same data
>> format but build instances of a different type.  Obviously I can just
>> define serialize() for each of them, but can I define only save for
>> the outgoing type and load for the incoming one, causing
>> serialization in the other direction to be a compile-time error?  Not
>> a big deal, but it would be more expressive that way.
>
> I'd use a wrapper type to have control over what types get instantiated on
> the receiving end. 

I can't picture what you mean, but it doesn't seem to address my question.

> This way you don't have to trick the serialization library into
> handling the same data format differently on the save and load ends.

I don't think there's any trickery involved.  I'll just

  ar << transmit_type;

  ar >> receive_type;

What am I missing?

-- 
Dave Abrahams
BoostPro Computing
http://www.boostpro.com