This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: egcs-1.0.2 STL problem?
- To: egcs at cygnus dot com
- Subject: Re: egcs-1.0.2 STL problem?
- From: Nathan Myers <ncm at cygnus dot com>
- Date: Fri, 10 Apr 1998 18:57:03 -0700
- Newsgroups: cygnus.egcs
- Organization: http://www.cantrip.org/
- References: <19980324135940.29107.qmail@hotmail.com>, <orsoo6sg5n.fsf.cygnus.egcs@zecarneiro.lsd.dcc.unicamp.br>
Alexandre Oliva wrote:
> egcs's STL is broken in this respect, because it defines two
> non-standard constructors:
>
> vector(int n, const T& value) { fill_initialize(n, value); }
> vector(long n, const T& value) { fill_initialize(n, value); }
>
> Now, since dummy_int is an lvalue (0 was not, so these constructors
> were not selected because they would involve the creation of
> temporaries), the first of these two constructors is selected as an
> exact match. But there constructors should not be defined, since they
> break ANSI/ISO C++ compliance.
>
> Unfortunately, stl_vector is imported as-is from the SGI
> implementation of STL. Would someone who is in touch with SGI
> developers please forward this message to them?
Matt knows about it. They should not be in the next release of
the SGI STL; likewise the next unsupported/isolib snapshot.
Nathan Myers
ncm@cantrip.org