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.9 required=5.0 tests=BAYES_00
	autolearn=unavailable autolearn_force=no version=3.4.4
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail
From: Simon Wright <simon@pushface.org>
Newsgroups: comp.lang.ada
Subject: Re: Handling transactions?
Date: Mon, 27 Jul 2015 15:53:00 +0100
Organization: A noiseless patient Spider
Message-ID: <lya8uhzm7n.fsf@pushface.org>
References: <d075fc4c-083d-4654-b04a-15f84c8511c9@googlegroups.com>
	<mp5e9k$ba2$1@dont-email.me>
	<6b5c318e-430d-4950-9762-e0ecdaa0ac9a@googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain
Injection-Info: mx02.eternal-september.org;
 posting-host="0b8a1d07de517ba95be21a60d7133ef5";
	logging-data="19606"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX1/P4BKT9KPPX3e6AhLaRQJHlwtlgEAXAsc="
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (darwin)
Cancel-Lock: sha1:PiZaGFRV3SU7GK3aSRFxm6E/La0=
	sha1:B6mn0TjDDlRXu+HbxKaOMWqAqDM=
Xref: news.eternal-september.org comp.lang.ada:27033
Date: 2015-07-27T15:53:00+01:00
List-Id: <comp.lang.ada>

EGarrulo <egarrulo@gmail.com> writes:

> Sorry, I didn't specify that I was not talking about database
> transactions -- albeit the concept is the same -- but rather about
> keeping an object in a consistent state even when exceptions occur
> during processing.  Since the realm of Ada is high-integrity systems,
> I suppose that this is a solved problem, but I haven't found any
> explanations in regard.

One approach to high-integrity systems requires you to prove, using for
example SPARK, that there can be no exceptions; then the problem doesn't
arise.