Sender: tim AT picard DOT skynet DOT be
Message-ID: <3ADC5ED9.63556C86@falconsoft.be>
Date: Tue, 17 Apr 2001 17:18:49 +0200
From: Tim Van Holder <tim DOT vanholder AT falconsoft DOT be>
Organization: Falcon Software NV
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16-3 i686)
X-Accept-Language: en, nl-BE, nl
MIME-Version: 1.0
To: fogels AT es DOT co DOT nz, djgpp AT delorie DOT com
Subject: Re: [C++] vector.at(int) function
References: <3AD0D79C DOT E6C48677 AT es DOT co DOT nz>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp AT delorie DOT com

Christo Fogelberg wrote:
> 
> Hi all,
> It seems to me that the current version of the STL that DJGPP uses
> doesn't support the vector.at() function - i.e. random access with
> bounds checking :(
> Is that just me? If not, does anyone know when the next 'official' DJGPP
> STL will be released? (I think they use the SGI library?)
> Cheers!
> Christo

First off, please note that the STL implementation you use comes with
gcc and not with DJGPP as such.
Secondly, the STL that comes with gcc (I assume you're using gcc 2.95.2
or later) is fairly outdated.

gcc 3 should have a greatly more standardized STL (several gnu
extensions
I liked were dropped however, such as ostream::form() and the less picky
istream::read()/ostream::write()). Unfortunately, gcc 3 has been in the
"soon to be released" stage for a while now, so I don't know how long
it'll
be before it's available.

If you're adventurous, you could even compile STLPort for DJGPP I
believe
(as I understand it that should work with few problems, but I'm not 100%
sure)

-- 
Tim Van Holder - Falcon Software N.V.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
This message was posted using plain text. I do not endorse any
products or services that may be hyperlinked to this message.