From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: fac41,9a0ff0bffdf63657
X-Google-Attributes: gidfac41,public
X-Google-Thread: f43e6,9a0ff0bffdf63657
X-Google-Attributes: gidf43e6,public
X-Google-Thread: 1108a1,9a0ff0bffdf63657
X-Google-Attributes: gid1108a1,public
X-Google-Thread: 103376,4b06f8f15f01a568
X-Google-Attributes: gid103376,public
From: Richard Melvin <rmelvin@radm.demon.co.uk>
Subject: Re: Software landmines (loops)
Date: 1998/09/02
Message-ID: <8ZxgNSAbqa71EwTM@radm.demon.co.uk>#1/1
X-Deja-AN: 387250454
X-NNTP-Posting-Host: radm.demon.co.uk:194.222.155.111
References: <slrn6sopmg.4fg.jdege@jdege.visi.com>
 <6renh8$ga7$1@nnrp1.dejanews.com> <6rf59b$2ud$1@nnrp1.dejanews.com>
 <l5HC1.6840$wN.1856764@news.giganews.com> <6rfra4$rul$1@nnrp1.dejanews.com>
 <35DBDD24.D003404D@calfp.co.uk> <m3ogt3qgca.fsf@mheaney.ni.net>
 <6sbuod$fra$1@hirame.wwa.com> <35f51e53.48044143@news.erols.com>
 <6sdiav$e0g$1@hirame.wwa.com> <u90k5f1j1.fsf@gsfc.nasa.gov>
 <6sfcft$70p$1@hirame.wwa.com> <6shp40$ec8$1@nnrp1.dejanews.com>
 <6sie46$eb7$1@hirame.wwa.com> <i53H1.1212$EW4.489160779@newsreader.digex.net>
 <6siijm$h1m$1@hirame.wwa.com> <m3ogsz74as.fsf@mheaney.ni.net>
 <6sjl6v$5qh$1@hirame.wwa.com>
X-Complaints-To: abuse@demon.net
X-Trace: news.demon.co.uk 904768515 nnrp-09:26137 NO-IDENT
 radm.demon.co.uk:194.222.155.111
Organization: n/a
MIME-Version: 1.0
Newsgroups: comp.lang.eiffel,comp.object,comp.software-eng,comp.lang.ada
Date: 1998-09-02T00:00:00+00:00
List-Id: <comp.lang.ada>

In article <6sjl6v$5qh$1@hirame.wwa.com>, Robert Martin
<rmartin@oma.com> writes
>
>Consider the case of a complex data structure.  You are in the midst of
>changing a set of variables within it.  Suddenly you realize that you must
>exit early.  Before you can exit, you have to put the data structure back
>the way it was.  In C++, getting a destructor to do this can be horrific.

This seems a weak argument, as there can easily be no way whatsoever to
put things back the way they were - the most obvious example is a sort
function.

(Unless you copy the initial state of the array before sorting, which
can be done just as easily in a little stack-based transaction object.) 

-- 
Richard Melvin