From: eplmst AT lu DOT erisoft DOT se (Martin Stromberg)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Windows ME and DJGPP
Date: 26 Jan 2001 12:47:00 GMT
Organization: Ericsson Erisoft AB, Sweden
Lines: 11
Message-ID: <94rrk4$sro$1@antares.lu.erisoft.se>
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>
NNTP-Posting-Host: lws256.lu.erisoft.se
X-Newsreader: TIN [version 1.2 PL2]
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:
: The only memory allocation problems that really can occur in C++ are NULL
: pointers (caught by the processor => SIGSEGV) and memory leaks (then you

That (getting SIGSEGV) won't work on WINDOZE if I'm not mistaken. Why
don't you try it and see for yourself?...


Right,

						MartinS