Re: [Boost-users] Serialization newbie, memory being overwritten?

Subject: Re: [Boost-users] Serialization newbie, memory being overwritten?
From: Lasse Laursen (gazoo_at_[hidden])
Date: 2012-12-02 21:12:00

I had thought along the same line. I think that's a good idea Nat. For 
now, I'm just using serialize to instantiate the object and then filling 
in the remaining fields. A bit hacky, but it works.

Regardless - I thank you for taking the time to help get my head on 
straight with regards to how serialization works in the context I was in 
Nat.

I appreciate it! :)

On 28-11-2012 22:43, Nat Linden wrote:
> On Tue, Nov 27, 2012 at 11:54 PM, Lasse Laursen <gazoo_at_[hidden]> wrote:
>
>> I'm all ears for an opinion on the approach. It would just appear to me that
>> serialization is appealing to keep the code simple and still be quite
>> flexible.
>
> What about breaking out the metadata you want to serialize as a class,
> or family of classes, separate from the audio data you don't need to
> serialize? You could make the audio class point to an instance of the
> concrete metadata class, or vice-versa, or have a holder class
> reference both. In any case, the point would be to de/serialize all
> fields of the metadata class.
>