From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Windows ME and DJGPP
Date: 25 Jan 2001 17:00:36 GMT
Organization: Aachen University of Technology (RWTH)
Lines: 27
Message-ID: <94pm3k$1qf$1@nets3.rz.RWTH-Aachen.DE>
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>
NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de
X-Trace: nets3.rz.RWTH-Aachen.DE 980442036 1871 137.226.32.75 (25 Jan 2001 17:00:36 GMT)
X-Complaints-To: abuse AT rwth-aachen DOT de
NNTP-Posting-Date: 25 Jan 2001 17:00:36 GMT
Originator: broeker@
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Rudolf Polzer <rpolzer AT web DOT de> wrote:
> Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de> schrieb folgenden Unsinn:
>> Compared to both of these, ME is a pain in the lower back as it comes
>> to advanced DJGPP usage. Just as an example, you'll have no way of
>> using the full power of the YAMD memory debugger on an ME system
>> without applying that highly unofficial patch to re-enable the real
>> MS-DOS sleeping inside it.

> But that is no argument:
> 1. if you are still programming in C it's no "advanced DJG_PP_ usage"

Please note that the _PP_ in DJGPP has absolutely nothing to do with
C++. Advanced usage to me means that you're a programmer who expects
more from a programming toolchain than just building programs.
Debugging tools like YAMD are advanced, in that sense.

> 2. if you are programming in C++, an overloaded operator new() and
> operator delete() will do.

You don't seem to have understood what YAMD really is, yet. YAMD is
better than anything you can do by redefining new()/delete() or
malloc()/free(), by a wide margin. No redefined allocation operator
will allow you to detect not only that, but *when* and *where* an
allocated buffer was overrun.
-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.