This is the mail archive of the
mailing list for the libstdc++ project.
Re: Seeming g++-specific "feature deficit"...
- From: Jonathan Wakely <jwakely dot gcc at gmail dot com>
- To: "Linda A. Walsh" <gcc at tlinx dot org>
- Cc: "libstdc++" <libstdc++ at gcc dot gnu dot org>
- Date: Sat, 4 Oct 2014 19:48:48 +0100
- Subject: Re: Seeming g++-specific "feature deficit"...
- Authentication-results: sourceware.org; auth=none
- References: <542F6960 dot 2050205 at tlinx dot org> <alpine dot DEB dot 2 dot 11 dot 1410040836130 dot 3813 at stedding dot saclay dot inria dot fr> <542FEFDA dot 1040205 at tlinx dot org>
On 4 October 2014 14:02, Linda A. Walsh <firstname.lastname@example.org> wrote:
> Marc Glisse wrote:
>>> So why not under gnu c++?
>> Because that is a non-standard function, obviously...
> So valarray isn't really part of the the
> STL and that's why many STL functions won't work with
It was not part of the STL, and is in the Numerics clause of the
standard, not the Containers clause.
>> Look for "begin".
>> You can write begin(group) but not group.begin().
> I can see I'd grouped valarray in with the STL
> containers... and thought it was part of the same
> paradigm. I'm just beginning to see how much of the
> STL functions won't work on it...
> Ick, I'll have to remember how much valarray doesn't
> fit into the STL standard container group... it really
> wasn't really that obvious how different it was from the
> rest for someone just being introduced to all of them
> at once.
As I'm pretty sure I've said before, you seem to be trying to use
valarray where it isn't suitable.