Date: Wed, 4 Aug 1999 09:49:27 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Shawn Hargreaves <ShawnH AT Probe DOT co DOT uk>
cc: djgpp AT delorie DOT com
Subject: Re: is djgpp object-oriented?
In-Reply-To: <8D53104ECD0CD211AF4000A0C9D60AE301549FFD@probe-2.acclaim-euro.net>
Message-ID: <Pine.SUN.3.91.990804094855.6630E-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Tue, 3 Aug 1999, Shawn Hargreaves wrote:

> > You can't even dereference a pointer in C++ without being sure it wasn't 
> > overloaded by some class that is called deep inside the libraries you are 
> > using.
> 
> For sure: that's why it is important to understand the language,
> and know what libs you are using.

No argument here.  The crux of the problem is that with C++, you need
a much more detailed knowledge of every single class library you are
linking in.  Since some of these libraries can come without sources,
it might be impossible or impractical to do that.  The level of trust
for library code, to say nothing of primitive operations like pointer
dereference, in C usually can be much higher, at least for ``normal''
application code that doesn't have to live with slow CPUs and small
memory size.