I wrote the following code:
#include
#include
#include
struct bar
{
std::string s3;
std::string s4;
}Ba
You can't use memcpy to copy objects or structure containing objects because they will not be properly initialized. Strings have pointers to char arrays, and if two strings can share the same pointer, there must be some kind of garbage collection (typically a reference counter). If you do f1.b1 = b2, the compiler will generate the code to initialize the strings correctly.
union foo
can't initialize the bar object (how does it know which member's initializer to call?) and consequently can't initialize the std::string
s. If you want to use the bar inside of foo, then you need to manually initialize it, like so...
new (&f1.b1) bar; // Placement new
f1.b1 = b2;
// And later in code you'll have to manually destruct the bar, because
// foo doesn't know to destruct the bar either...
f1.b1.~bar();
Alternatively, you can try to roll this functionality into the union's constructors and destructors yourself.
foo() : b1() {}
// Or you construct like this, which you might need to for a non-trivial union...
// foo() { new (&b1) bar; } // Placement new.
~foo() { b1.~bar(); }
Note that copying also needs special handling.
std::string
has a non-trivial constructor, that initializes its internal members. Therefore, your struct bar
is no POD structure.
Unions only support POD (this is relaxed in C++11). The compiler cannot decide which constructor of which of the union's members to call. Imagine following situation:
unition MyUnion {
std::string s;
std::vector v;
};
Should it use vector's or string's constructor to initialize the object?
So in your situation, when you assign the string to the union's string, the internal data is not initalized, which causes random errors.