views:

355

answers:

2

boost::variant claims that it is a value type. Does this mean that it's safe to simply write out the raw representation of a boost::variant and load it back later, as long as it only contains POD types? Assume that it will be reloaded by code compiled by the same compiler, and same version of boost, on the same architecture.

Also, (probably) equivalently, can boost::variant be used in shared memory?

+5  A: 

Regarding serialisation: It should work, yes. But why don't you use boost::variant's visitation mechanism to write out the actual type contained in the variant?

struct variant_serializer : boost::static_visitor<void> {
    template <typename T>
    typename boost::enable_if< boost::is_pod<T>, void>::type
    operator()( const T & t ) const {
        // ... serialize here, e.g.
        std::cout << t;
    }
};

int main() {

    const boost::variant<int,char,float,double> v( '1' );

    variant_serializer s;
    boost::apply_visitor( s, v );

    return 0;
}

Regarding shared memory: boost::variant does not perform heap allocations, so you can place it into shared memory just like an int, assuming proper synchronisation, of course.

Needless to say, as you said, the above is only valid if the variant can only contain POD types.

I'd like to avoid writing lots of boilerplate code to write out said actual types :)
bdonlan
not much boilerplate code needed; see above
+1  A: 

Try just including boost/serialization/variant.hpp; it does the work for you.

spiderlama