
I am hopeful that progress will soon be made on this area. This would accomplish: a) fixing noted bugs in the portable binary archive and making it pass the serialization torture tests that the other archives are subjected to. b) subjecting it (along with other archives) to profiling at least with gcc compilers. I wasn't planning on addressing floating point. If someone wants to do this I would certainly be happy to lend my constructive criticism to the effort. The main issues are: a) portable subset of NaN's etc. It seems to me this is ready to that this code has been done by John Rade? so that's would seem ok. b) portable encoding of floating point - a very attractive proposal was submitted some time ago (with code !!!) by Ralf W Grosse-Kunstleve search the mailing list for this. So feel free to get busy. Robert Ramey Pfligersdorffer, Christian wrote:
So, is there anything going on in this cause? I really need floating point types so I'd love to see some progress in that. I am also willing to do some coding if need be.
Regards,
"Scott McMurray"
wrote: FWIW, I'm currently using binary files for some work because the text is huge and slow.
... down to 1.2 GiB instead of the 2.1 GiB for text ... It also makes my load time drop from a few minutes to a few seconds
This has been my (somewhat limited application domain) experience, as well. Almost all of the distributed systems I've worked on that used binary message data passing did so for both processing speed and compactness of the data. Most of the system architects understood the "brittleness" and drawbacks of the design (specially when floating point values were needed), but were willing to make the tradeoff.
I'd love to be able to remove at least some of the code design and portability drawbacks for applications needing to pass (or read / write) binary data.
Cliff _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users