Date: Thu, 25 Jan 2001 13:07:54 -0500
Message-Id: <200101251807.NAA27769@envy.delorie.com>
X-Authentication-Warning: envy.delorie.com: dj set sender to dj AT envy DOT delorie DOT com using -f
From: DJ Delorie <dj AT delorie DOT com>
To: djgpp AT delorie DOT com
In-reply-to: <slrn970p9v.28f.rpolzer@rebounce.rpolzer-lx>
Subject: Re: Windows ME and DJGPP
References: <20010120205730 DOT 25849 DOT 00000491 AT ng-fd1 DOT aol DOT com> <3a6b7917 DOT 10793503 AT news DOT sci DOT fi> <3A6CB71F DOT 8B4E86C9 AT phekda DOT freeserve DOT co DOT uk> <94k3dc$lf9$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE> <slrn96u191 DOT 2cl DOT rpolzer AT rebounce DOT rpolzer-lx> <94pm3k$1qf$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE> <slrn970p9v DOT 28f DOT rpolzer AT rebounce DOT rpolzer-lx>
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


> Overruns do not occur in C++ code, the STL checks everything (including
> wrong indices of a vector). Only poor-style C++ code (or system-level code
> which then is in C) uses C arrays, malloc and free.

Sorry, this is just blatantly false.  I've written some really heavy
duty C++ code with C arrays, malloc, and free, and not had memory
problems with it (nor would I consider it poor style, as I did use the
C++ features *appropriately* for the project).  Use of STL has nothing
to do with the C++ language; you could write a C equivalent of STL
that has the same protection, but that would not change anything about
the C language itself.

Whether code is "poor-style" or not depends on the programmer, not the
language.