Boost logo

Boost :

Subject: Re: [boost] [Endian] Review
From: Vicente J. Botet Escriba (vicente.botet_at_[hidden])
Date: 2011-09-09 15:20:13


Le 09/09/11 15:05, Beman Dawes a écrit :
> On Fri, Sep 9, 2011 at 2:32 AM, Vicente Botet<vicente.botet_at_[hidden]>wrote:
>
>> Hi,
>>
>> I have separated the endian class into a endian_pack that is integer
>> agnostic and an endian class that behaves as an integer (You could see the
>> details in the Sandbox under endian_ext).
>>
>> Reference docs:
>>
>> http://svn.boost.org/svn/boost/sandbox/endian_ext/libs/integer/endian/doc/html/toward_boost_integer_endian/reference.html#toward_boost_integer_endian.reference.integer_endian_pack_hpp
>>
>>
>> http://svn.boost.org/svn/boost/sandbox/endian_ext/libs/integer/endian/doc/html
>>
>> (Sorry but there is a bad link to the reference)
>>
>> This is not complex
>
> Complexity is in the eye of the beholder. To me, that approach was markedly
> more complex and confusing.
>
What do you find complex in separating the classes endian_pack and endian?
>> and allows to define physical structures that can be
>> used only at the I/O frontier.
>>
> See my reply to Phil Endecott (this morning, 9/9/11) for an example of doing
> this.
>
Well, IIUC your replay doesn't force the separation of concerns. Of
course, the user of such a structure could do the separation, but the
interface doesn't force it.

Best,
Vicente


Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk