Question

so I’m using the boost::serialization library, and I’m trying to overide how a class is constructed, since it has no default constructor. This is demonstrated here. To me it appears the function takes the class* t and then sets it to point to a newly constructed object. If i’m wrong, this is definately the source of my error.

However, the only way to construct my class is by using another classes create() function, meaning I need to stray from the code in the example (this is stated in the boost::serialization namespace): ::new(t)my_class(attribute);

I tried simply calling the create function and setting t equal to the returned pointer, but this doesn’t seem to work because right after the load_construct_data function, and in the serialization function, the given myClass& is not the same as what I set ‘t’ to.

How do I do whatever ::new(t) is doing so the object created using the create function follows through into the serialize/other functions?

Answer 1

The construct referred to in your question (new(t) my_class(attribute)) is called “placement new”. The way it work is that

1. t must already point to an allocated region of memory (placement new doesn’t do allocation by default)
2. An instance of my_class is constructed at that memory location.

However, since in your case you can’t use constructors, then using any form of new is out of the question. But there is an alternative (sort of).

Since placement new pretty much just overwrites a chunk memory, we can use a regular function which does the same with an already constructed object. Such a function is memcpy:

void * memcpy ( void * destination, const void * source, size_t num );

All memcpy does is perform a byte-wise copy of num bytes from the memory pointed to by source to the memory pointed to by destination.

So let’s say you started with this code in the load_construct_data

my_class obj = other_class::create();

Then we can use the memcpy function to “move” the value at obj into the memory reference by t:

memcpy((void*)t, (void*)(&obj), sizeof(obj));

While there are some details about how this works with your particular class, such as whether a bit-wise copy is “good enough”, this is the best I’ve got with what you’ve asked. The one problem I see is if the destructor releases resources, than the copy will may become invalid.

To account for the possible problems with destruction, you can write your own deep copying function:

void deepCopy( my_class * destination, const my_class * source );

which you call instead of memcpy.

Note: please tell me if I went astray with anything here. I don’t currently have a machine to test code on.