Re: [boost] [endian] endian flip and endian domain

Subject: Re: [boost] [endian] endian flip and endian domain
From: Stewart, Robert (Robert.Stewart_at_[hidden])
Date: 2010-06-09 06:46:03

Gottlob Frege wrote:
> On Tue, Jun 8, 2010 at 1:05 PM, Dave Handley
> <Dave.Handley_at_[hidden]> wrote:
>
> I'll admit to having a habit of over-thinking on names. But they are
> important.

Ditto.

> - "cast" if the syntax matches.
> - "convert" otherwise

That's a reasonable taxonomy and one that can be explained readily.  "cast" should be named "endian_cast" based upon earlier discussion, even if it lives in a boost::endian namespace.  The word "endian" need not be added to "convert" as it is obviated by template argument(s) and the namespace name.

> "convert", to me, matches most closely with what you express - ie,
> "What term does everyone use..."  Yes, 'swap' might be the first term,
> but I think, by re-reading the emails, that "convert" comes in second,
> clearly ahead of the rest.  That's actually why I suggested it - it
> was the term everyone was using.   And without the problems swap has.

I adopted "convert" specifically because I tried to stop using "swap," so yes, it is a suitable word for the purpose and a reasonable second choice.

_____
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.