xt knight wrote:
Is there anything that can be done to fix the problem? Its behavior
doesn't match the docs.
The docs could be fixed?
Seriously, I have trouble understanding why people care about a few
gratuitous digits. But, well.
Let's see: We cannot "fix" the libraries output routine because doing so
would destroy "print-read consistency" (this is the property
read(print(x))==x). We can, however stuff the entire output in a C++
std::stringstream object and cut off the last few digits there. I think
we can do that. BUT: I'll only accept such a patch if it does not slow
down the program significantly (it probably won't), and only if the
excess memory is less than the maximum memory required earlier when
doing the computation (no idea, will have to run through valgrind
--tool-massif).
Can you provide such a patch?
-richy.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
