It would be any archive which alters the of bytes from that used by the native machine. The implementation of portable binary archive (which had/has) a few issues anyway, renders the byte stream in an manner independent of the int size and endian-ness. So it fails. I never thought about this until I came upon it by accident. So I have no idea when it will come up again. What bothers me more about it is that now I can derive from a known archive according to the documentation, and have an implementation which full fills the stated requirements but won't work. I suspect that there needs to be some additional concept added to the binary_?archives that other archive classes don't have. But truth is, I really haven't considered it detail. I was sort of annoyed that the example used to illustrate derivation from an existing archive has to be redone. as I didn't find out about it until recently, so the next release includes a demo and documentation that doesn't work without any real time to fix it. Robert Ramey Matthias Troyer wrote:
On 28 Nov 2007, at 17:32, Robert Ramey wrote:
Unfortunately, recent changes in binary_?archive break any archive classes derived from it - this includes the portable binary demo included in the package and probably other archives as well.
Robert, could you please send me a single example, outside of your portable binary archive demo that would need to be updated, where the array extensions break anything?
Matthias