Re: [boost] [boost::endian] Summary of discussion #1

Subject: Re: [boost] [boost::endian] Summary of discussion #1
From: Stewart, Robert (Robert.Stewart_at_[hidden])
Date: 2010-06-04 06:50:10

Terry Golubiewski wrote:
>
> It's easy for me to suggest that someone else should change.
> But what would such a change look like.
> How about this... (I've ignored alignment)
>
> namespace boost { namespace interface {

boost::interface strikes me as a meaningless namespace.

> template<size_t Bits,  endian_t Endian=native>
> class PackedInteger {
> public:
>    typedef typename boost::int_t<Bits>::least value_type;
>    static const endian_t endianness = Endian;
[snip]
>    PackedInteger(): { m_storage.fill('\0'); }
>    explicit PackedInteger(value_type x) { store(x); }

Why explicit?

>    operator value_type() const { return retrieve(); }
>    PackedInteger& operator=(value_type x) { store(x); }
>    // All the usual integer operations go here.
> }; // PackedInteger
>
> } } // boost::interface

I don't understand the point of "packed" in the name.  I'd have expected boost::endian to be what Beman has now minus arithmetic operators and then boost::endian_integer to be derived from boost::endian with the arithmetic operators.  That seems simple and obvious.  Have I missed something?

_____
Rob Stewart                           robert.stewart_at_[hidden]
Software Engineer, Core Software      using std::disclaimer;
Susquehanna International Group, LLP  http://www.sig.com

IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.