[boost] Re: Re: Re: Re: char[] support in Boost.Range

From: Thorsten Ottosen (nesotto_at_[hidden])
Date: 2005-05-17 15:39:23

"dan marsden" <danmarsden_at_[hidden]> wrote in message 
news:20050517202600.13327.qmail_at_web25106.mail.ukl.yahoo.com...
|> Anyway, that wasn't my point. My point was that
| > it is really easy to get the array behavior if you
| > want it.
| >
| > The only part missing is direct support in the range
| > library
| > to trigger array behavior for range arguments, say
| > as_array().
|
| It seems strange to need to force the more basic
| behaviour of an unconstrainted array of chars with
| zero cost for establishing the bounds, and default to
| higher level behaviour implying a delimiter and a
| linear cost to calculate the bounds.
|
| Some of this depends on what you perceive as the
| common case, but the differing behaviour between
| char[N] and MyType[N] presents a lack of uniformity
| that could hurt generic code developers and confuse
| users.

I'm not much interested in using naked arrays my-self, with the exception
of literals.

Would it be ok with people if const char[N] was the only
special case?

(Afterall, that type is not much use as a buffer)

-Thorsten