Boost logo

Boost :

From: David Abrahams (david.abrahams_at_[hidden])
Date: 2001-09-26 09:15:46

OK. Daryle, if you will change "iteratible" to "iteratable" I will accept
your submission as is. Feel free to email it to me personally. Please don't
make any other changes though, because they would cause another review
iteration ;-)


----- Original Message -----
From: "Aleksey Gurtovoy" <alexy_at_[hidden]>
To: <boost_at_[hidden]>
Sent: Wednesday, September 26, 2001 7:12 AM
Subject: RE: [boost] Re: Separate iterator operators from iterator traits?

> David Abrahams wrote:
> > I was hapy with bidirectional_iterator_operators, but
> > "bidirectional_iteratible" doesn't work at all for me.
> Apparently, '[...]_iterator_operators' names (that I like too) don't fit
> well into the general naming convention used through the rest of the
> (that is documented in our "Summary of Template Semantics"; in particular,
> item 2 of that section says: "The name of an operator class template
> indicates the /concept/ that its target class will model").
> > I'm not sure if "iteratible" is a word, but if it is, I think
> > it would be spelled "iteratable". In any case, I'd like to
> > hear from others about the choice of names. Jeremy?
> > Aleksey?
> IMO if you think about "[input,output,..]_iteratable" as a name of the
> concept, it becomes an acceptable choice. At least I am ok with it. FWIW,
> Google search on "iteratable" finds ~70 distinct pages where the word is
> used, mostly in CS texts, and at least one seemed to talk about higher
> mathematics :).
> Aleksey
> Info: Unsubscribe:
> Your use of Yahoo! Groups is subject to

Boost list run by bdawes at, gregod at, cpdaniel at, john at