<span class="Apple-style-span" style="font-family: arial, sans-serif; background-color: rgb(255, 255, 255); font-size: medium; "><pre>> Just use boost::variant. Serialization is already implemented for it > and it effectively does the above. It does a bunch of other stuff > as well which is likely useful for your application.</pre></span><div>I've tried boost.variant with the full typelist, but it seems gcc 4.4 balks at typelists longer than 60, and I have over 104 types and growing. Perhaps there is some workaround for extremely long type list lengths that I'm not aware of?</div> <div><br></div><div>Sorry I'm not below your message, I didn't get the email directly to my address so I'm not sure how to do it indirectly.</div><div><br></div>Cheers!<div>Andrew Hundt</div><br> <br><br><div class="gmail_quote">On Tue, Aug 30, 2011 at 6:27 PM, Andrew Hundt <span dir="ltr"><<a href="mailto:athundt@gmail.com">athundt@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> <div>I have an unusual use case for boost.serialization, and I was wondering if it would be possible to adapt it to my needs:</div><div><br></div><div>-�I have a set of over 100 types, and instances of each are generated asynchronously then serialized to a file in that order.�</div> <div>- The most interesting serialized data will be written just before the power is unexpectedly cut.</div><div>- I need to load in and run on as much data as possible when reading the serialized data back, ignoring incomplete data at the end (due to a power cut).�</div> <div>- The basic Boost serialization examples require you to know the type of the next piece of data to be loaded when reading.�Since these types are generated asynchronously they are not known in advance. �</div><div>-�I need to write the data out immediately when it arrives because of the power issue.�</div> <div>- Files will be getting up to around 150GB in size for binary archives, so it can't be�marshaled�in memory, it needs to be written immediately even if it is redundant.</div><div><br></div><div>Is there a way to read in that serialized file using the facilities provided in boost.serialization?</div> <div><br></div><div>I could also�serialize an index or custom headers indicating the next type to appear, I would prefer to avoid doing so.</div><div><br></div><div>One way of achieving some of these goals is writing one piece at a time using a binary archive to an fstream. But I don't know what aspects of my requirements will prove to be a problem.</div> <div><br></div><div>Thanks for your thoughts.</div><div><div><br></div>Cheers!<div>Andrew Hundt</div><br> </div> </blockquote></div><br>