Boost logo

Boost :

Subject: Re: [boost] [Review:Algorithms] is_ordered behaviour for singleton input, and name
From: Greg Rubino (bibil.thaysose_at_[hidden])
Date: 2011-09-23 14:21:20


On Fri, Sep 23, 2011 at 2:13 PM, Stewart, Robert <Robert.Stewart_at_[hidden]>wrote:

> Greg Rubino wrote:
> > On Sep 23, 2011 12:39 PM, "Marshall Clow"
> > <mclow.lists_at_[hidden]> wrote:
>
> I agree with Phil's concern about is_ordered suggesting that the return
> type is Boolean.
>
> > > "disorder" doesn't sit quite right with me for some reason.
> > >
> > > How about "ordered_until", maybe?
> > >
> > > or "find_unordered"
> >
> > +1 for "find_unordered".
>
> That's pretty good, but it made me think of the unordered containers, and
> then that it would find the unordered containers in a sequence. Stupid?
> Yes. Nevertheless, that was my thought sequence (pun intended).
>
>
That's funny. I thought of unordered_<containers> as well when I read that,
but I had a positive reaction to that thought sequence since the semantics
of the word 'unordered' are congruent in both contexts. However, I do think
that the 'find_' prefix changes the scope to elements of the container
rather than the container as a whole (as in unordered_<container>).

I actually really like find_disorder(), because it makes it sound more
righteous, but find_unordered() is less likely to offend more delicate
sensibilities.

> Go with "find_unordered".
>

++1; // syntax error

>
> _____
> Rob Stewart robert.stewart_at_[hidden]
> Software Engineer using std::disclaimer;
> Dev Tools & Components
> 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.
>
> _______________________________________________
> Unsubscribe & other changes:
> http://lists.boost.org/mailman/listinfo.cgi/boost
>


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