From -140557278320590261
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: f78e5,df06663c0326d841
X-Google-Attributes: gidf78e5,public
X-Google-Thread: 109fba,df06663c0326d841
X-Google-Attributes: gid109fba,public
From: James Kuyper <kuyper@wizard.net>
Subject: Re: auto_ptr copy semantics
Date: 1999/06/01
Message-ID: <375421A7.5444DAAB@wizard.net>#1/1
X-Deja-AN: 484549916
X-NNTP-Posting-Host: gscsgi01.gsfc.nasa.gov
Content-Transfer-Encoding: 7bit
Approved: stephen.clamage@sun.com (comp.std.c++)
References: <7el5br$kjj$1@nnrp1.dejanews.com> <MPG.117c078a69a24c459896e7@client.sw.news.psi.net> <7f0i8a$sc9$1@nnrp1.dejanews.com> <bill-1404991010270001@bgibbons.vip.best.com> <7f5bhs$vgm$1@nnrp1.dejanews.com> <IwfY2.623$AL5.1214@ndnws01.ne.mediaone.net> <7gvibk$tkl$1@nnrp1.deja.com> <SwNY2.1714$AL5.1935@ndnws01.ne.mediaone.net> <7h4q93$ptn$1@nnrp1.deja.com> <M68_2.2684$AL5.3741@ndnws01.ne.mediaone.net> <7if3ih$frk$1@nnrp1.deja.com> <gQ333.10309$AL5.44301@ndnws01.ne.mediaone.net> <7j0vaq$86c$1@nnrp1.deja.com>
X-Accept-Language: en, es, de, ru
X-UID: 0000000001
X-Status: $$$T
Content-Type: text/plain; charset=us-ascii
Organization: NASA Goddard Space Flight Center -- Greenbelt, Maryland USA
Mime-Version: 1.0
Newsgroups: comp.lang.c++,comp.std.c++
Originator: clamage@taumet


sirwillard@my-deja.com wrote:
> 
> In article <gQ333.10309$AL5.44301@ndnws01.ne.mediaone.net>,
>   "Dave Abrahams" <abrahams@mediaone.net> wrote:
> > > It is nigh unto impossible to recover from memory allocation
> failures.
> >
> > Sir, A claim that it's impossible is unlikely to impress me, since I
> have
> > done it successfully myself many times, and have subjected the
> recovery code
> > to rigorous tests.
> 
> *Ahem*  "It is nigh unto impossible" doesn't say it's impossible, but
> close enough to require proof that it can be done.  The burden of proof
> is on your shoulders, not mine (and a claim that you've done it isn't
> enough).  The other thread deals with this issue extensively, pointing
> out why I claim it's "nigh unto impossible".  In a multitasking
> environment one can NOT fully protect an application from memory
                          ^^^^^

You just raised the bar. Your initial claim was that it was nearly
impossible to recover from memory allocation failures; such a claim
could be refuted by demonstrating an method that recovered from 10% of
all such failures. However, even a method that recovered from 99.9% of
all such failures wouldn't meet your new standard, since the remaining
0.1% of the case indicate that it's not fully protected.


[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@ncar.ucar.edu    ]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://reality.sgi.com/austern_mti/std-c++/faq.html              ]




