Re: [boost] Any interest in bitstream class?
On Jun 28, 2013, at 6:50 PM, Paul Long
wrote: Correct, but it is important to note that integrals are always encoded big endian in the bitstream. I >>suppose it's possible that someone would want some other endian, but that's got to be an obscure use >>case.
There are plenty of little endian only contexts that would want to avoid
From: Rob Stewart the host->network->host
conversions for all transfers.
The C++ Middleware Writer uses a "receiver makes right" approach to support that. There's a SameFormat class here: http://webEbenezer.net/misc/Formatting.hh that's used when both sides have the same endian-ness. -- Brian Ebenezer Enterprises - Was Eisenhower the last decent US President? http://webEbenezer.net
On 6/29/2013 3:54 PM, Brian Wood wrote:
The C++ Middleware Writer uses a "receiver makes right" approach to support that. There's a SameFormat class here: http://webEbenezer.net/misc/Formatting.hh that's used when both sides have the same endian-ness.
An "anti-goal" of the proposed bitstream library is that it is _not_ a serialization tool, such as CMW: https://github.com/dplong/bstream/wiki/Goals I'm not saying that the technique you mention does not apply to bitstream--I haven't looked into it--but I did want to put this out there. Paul
participants (2)
-
Brian Wood
-
Paul Long