Sender: nate AT cartsys DOT com
Message-ID: <36BF8B02.A08B5F86@cartsys.com>
Date: Mon, 08 Feb 1999 17:10:26 -0800
From: Nate Eldredge <nate AT cartsys DOT com>
X-Mailer: Mozilla 4.08 [en] (X11; I; Linux 2.0.36 i586)
MIME-Version: 1.0
To: djgpp AT delorie DOT com
Subject: Re: Getting new to throw bad_alloc.
References: <3 DOT 0 DOT 6 DOT 32 DOT 19990206235957 DOT 008ed6d0 AT pop DOT netaddress DOT com> <79l6v2$fp4$1 AT news DOT doit DOT wisc DOT edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp AT delorie DOT com

Mumit Khan wrote:
> 
> In article <3 DOT 0 DOT 6 DOT 32 DOT 19990206235957 DOT 008ed6d0 AT pop DOT netaddress DOT com>,
> Paul Derbyshire  <djgpp AT delorie DOT com> wrote:
> >In djgpp 2.02, does new throw bad_alloc?
> 
> Depends on the compiler and runtime of course. EGCS-1.1.x does throw
> bad_alloc. I have no idea what compiler comes with djgpp 2.02, so I
> don't know if it's supposed to or not.

No compiler "comes with" any particular DJGPP version; they're packaged
separately.  But GCC 2.8.1 is considered standard.
 
> Older releases did not have standard compliant implementation.

-- 

Nate Eldredge
nate AT cartsys DOT com