Re: internal compiler error in C++ front end

[Bob Sidebotham <rns at fore dot com>]

I'll bite: I'm desparate for namespace support. If someone will commit
to doing the namespace support, I'll write the STL tests: I know how
to do that, but I don't know how to do the namespace support. I'm
willing to put in effort to get the namespace support, and if that
means writing STL tests or doing other grunt work that comes along,
I'd be happy...

On the other hand, if someone gave me some pointers on how to approach
the namespace stuff, I'd be willing to give it a try...

Bob Sidebotham

You said:
>>>>>> Joe Buck <jbuck@synopsys.com> writes:
>
>> It seems that there is some confusion between vector<T>(size_type,const T&)
>> and the template member vector<T>(Iterator,Iterator).  The odd thing
>> is that for vector<int>(32,3) the second seems in some ways a better match,
>> but STL is banking on the first one being chosen! (to get a vector of
>> 32 elements with value 3).
>
>I believe the plan is to make the second one DTRT in this case.
>
>> While it's likely that this particular case would not have been
>> caught, this does suggest that the libstdc++ tests are too weak; tvector
>> does not try out even 1/10 of the vector class functionality.  Tests that
>> at least call each method of vector (and the other STL classes) at least
>> once would be a great help.  (Perhaps others already have something: the
>> ObjectSpace free tests seem too weak).
>
>Yep.  Contributions welcome.
>
>Jason