Re: [C++] Initialization lists with array
From: James Dennett (jdennett_at_acm.org)
Date: 04/01/04
- Next message: James Dennett: "Re: stack display"
- Previous message: James Dennett: "Re: [C++] Initialization lists with array"
- Maybe in reply to: James Dennett: "Re: [C++] Initialization lists with array"
- Next in thread: Chris \( Val \): "Re: [C++] Initialization lists with array"
- Reply: Chris \( Val \): "Re: [C++] Initialization lists with array"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 31 Mar 2004 20:39:20 -0800
Chris ( Val ) wrote:
> "Gary Labowitz" <glabowitz@comcast.net> wrote in message
> news:hO2dnfdXrrh1Iv7dRVn-hA@comcast.com...
> | "Chris ( Val )" <chrisval@bigpond.com.au> wrote in message
> | news:c3rv7m$2bvs7r$1@ID-110726.news.uni-berlin.de...
> | >
> |
> | > In essence, just because we can apply an algorithms to the
> | > std::string class, does not mean that we should call it a
> | > container class. Btw(please correct me if I'm wrong), but I
> | > had thought that the std::string class had already been written,
> | > prior to the adoption of the STL by the committee ?
> |
> | But it does container a sequence of char's. Doesn't that make it a container
> | candidate?
>
> Yes, it does container a sequence of char's, but so does a
> standard character array, of which algorithms can be applied
> to as well.
But an array lacks begin() and end(), so it's not a
container in the sense of the C++ standard. It also
fails to have a nested size_type member, and plenty
of other things. std::string has them, no?
-- James
- Next message: James Dennett: "Re: stack display"
- Previous message: James Dennett: "Re: [C++] Initialization lists with array"
- Maybe in reply to: James Dennett: "Re: [C++] Initialization lists with array"
- Next in thread: Chris \( Val \): "Re: [C++] Initialization lists with array"
- Reply: Chris \( Val \): "Re: [C++] Initialization lists with array"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|