From: apsh AT ecr DOT mu DOT oz DOT au (Alistair_P SHILTON)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Strange behaviour of new/delete
Date: 8 Jun 2000 02:34:25 GMT
Organization: Computer Science, University of Melbourne
Lines: 37
Message-ID: <8hn0nh$hc0$1@mulga.cs.mu.OZ.AU>
References: <8hknqj$gki$1 AT mulga DOT cs DOT mu DOT OZ DOT AU> <393DF410 DOT 93824118 AT earthlink DOT net> <8hkthr$kda$1 AT mulga DOT cs DOT mu DOT OZ DOT AU> <8F4C86B4FNiklasPsonnospamhotm AT 130 DOT 235 DOT 20 DOT 4>
NNTP-Posting-Host: gromit.ecr.mu.oz.au
X-Trace: mulga.cs.mu.OZ.AU 960431665 17792 128.250.61.61 (8 Jun 2000 02:34:25 GMT)
X-Complaints-To: usenet AT cs DOT mu DOT OZ DOT AU
NNTP-Posting-Date: 8 Jun 2000 02:34:25 GMT
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

OK, so I guess I can safely not worry about it then - good, I like that.


Yes.  The function is to remove a row/column from a lower triangular matrix
class like:

#
##     ->     #
**\           ##
##|#          ###

and the function must return the arrays ** and | and also the number \.  I
figured that double** was the simplest solution.  And it mostly works, with
the one exception I mentioned (but that's almost always the case :).

Niklas Pettersson (Niklas_Pson AT nosmam DOT hotmail DOT com) wrote:
: operator new throws a exception on failure (bad_alloc). You can catch this
: with a catch statement or just let it pass (in that case the program will 
: call abort automagical). The chance that new will fail is however very 
: small since the harddrive can be used to simulate a very large virtual 
: memory.. Just of couriousity, why do you use double** in this way? Is it an 
: imlementation of a matrix or something?


: / Pson



--
----------------------------------------------------

Alistair Shilton

http://www.ee.mu.oz.au/pgrad/apsh