Hello, Robert Ramey wrote:
Martin Ecker wrote:
One way of achieving all this would, of course, be to derive from one of the existing archive classes and add the required functionality. However, we don't want to lose the flexibility of being able to write out data to a binary, text, XML, or any other archive with some other kind of representation. So basically we're looking for a good way of inserting an additional layer in between the archives and the actual serialize functions that can store state variables.
Have you consider making a template which takes the base class as a parameter? Example
Ah, that's a nifty idea. I'll investigate this some further, but I believe this is just what we need. Thanks, Martin TAB Austria Industrie- und Unterhaltungselektronik GmbH & CoKG http://www.tab.at