I've run into a situation where I'm triggering an assertion at
basic_binary_oprimitive::save_binary(). This is on
basic_binary_oprimitive.hpp, line 115 in version 1.32. This assertion
seems to be claiming that an output stream will always be in a "good"
state after a call to write(). On it's face, I think there's no way to
safely make that claim, especially about a stream whose type is a
template parameter. In fact, as I understand it, good()'s whole purpose
is to let you know that the stream is busted.<br clear="all"><br>
Am I misunderstanding something, or should that assert be changed to an exception? <br>
<br>
I'm trying to get an example program that demonstrates this problem.
Currently, the code that exercises it is big and hairy, and I haven't
pared down the precise conditions that cause it to happen. I can
provide a stack trace, however, which may be of some use.<br>-- <br>Austin Bingham<br><br>&quot;If I were creating the world I wouldn't mess about <br>with butterflies and daffodils. I would have started <br>with lasers, eight o'clock, Day One!&quot; 
<br>Evil