James Dennett wrote: There isn't. I'm not sure there should be. Its only needed for xml archives but adding it would require that it be put in all the other archives as a no-op. Also "flush" suggests that one could continue using the archive after it was "flushed" like a stream. This would not be case as the function of "flush" would be to finish off the xml data structure. Ideally what I would like to do is throw an exception in the archive destructor if the stream is still open - but that's not a good idea.
Is there an explicit way to flush the archive before reaching its destructor? Presumably writing output to a stream can cause an exception to be thrown, and we would want to be able to handle such errors rather than hitting terminate().
-- James