Re: [boost] [string] proposal

Subject: Re: [boost] [string] proposal
From: David Bergman (David.Bergman_at_[hidden])
Date: 2011-01-27 13:16:17

On Jan 27, 2011, at 10:22 AM, Dean Michael Berris wrote:

> On Thu, Jan 27, 2011 at 11:13 PM, Sebastian Redl
> <sebastian.redl_at_[hidden]> wrote:
>> 
>> On 27.01.2011, at 04:54, Dean Michael Berris wrote:
>>> 
>>> I just prefer calling a spade a spade and not say `string` when I
>>> really mean a `view<encoding>` -- because largely I think everyone
>>> would agree that the string data structure really doesn't have an
>>> intrinsic property that relates to an 'encoding'.
>> 
>> The string data structure that I learned about in some obscure algorithm lectures in university and the thing that's represented by the type 'string' or some spelling variation of it in most programming language are really not the same thing. In particular, the latter is a type meant to store text, whereas the former is a sequence of something.
>> 
> 
> Exactly.
> 
>> That makes for a huge difference in my mind.
>> 
> 
> Definitely. Which is why I still think about a string and think "oh,
> sequence of something" rather than see string and think "oh, text!".

Ok, so we are back to std::vector again...

Is that the "boost::string" class you are proposing? Although immutable...

So, we should rid the notion of silly text-handling and focus on the sequentiality of a (CS...) string?

/David