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,FREEMAIL_FROM
	autolearn=unavailable autolearn_force=no version=3.4.4
X-Received: by 2002:a37:8905:: with SMTP id l5mr44495859qkd.152.1568337252347;
        Thu, 12 Sep 2019 18:14:12 -0700 (PDT)
X-Received: by 2002:a05:6830:1597:: with SMTP id
 i23mr9026988otr.182.1568337251974;
 Thu, 12 Sep 2019 18:14:11 -0700 (PDT)
Path: 
 eternal-september.org!reader01.eternal-september.org!feeder.eternal-september.org!news.gegeweb.eu!gegeweb.org!usenet-fr.net!proxad.net!feeder1-2.proxad.net!209.85.160.216.MISMATCH!o24no1347788qtl.0!news-out.google.com!x7ni192qtf.0!nntp.google.com!o24no1347781qtl.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Thu, 12 Sep 2019 18:14:11 -0700 (PDT)
In-Reply-To: <qla985$2vb$1@gioia.aioe.org>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com;
 posting-host=2601:193:4103:71a0:3105:36e3:feed:ebc;
 posting-account=1tLBmgoAAAAfy5sC3GUezzrpVNronPA-
NNTP-Posting-Host: 2601:193:4103:71a0:3105:36e3:feed:ebc
References: <fc3ac55b-d5c8-4255-9889-7f4b3fe428d0@googlegroups.com>
 <ql8sk7$6de$1@gioia.aioe.org>
 <a1312e9e-0724-4e87-98da-a38c54784f03@googlegroups.com>
 <qla985$2vb$1@gioia.aioe.org>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <067d5a1d-a17d-46d1-8627-e904099d0621@googlegroups.com>
Subject: Re: potential Ada feature - comments?
From: Matt Borchers <mattborchers@gmail.com>
Injection-Date: Fri, 13 Sep 2019 01:14:12 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Xref: reader01.eternal-september.org comp.lang.ada:57141
Date: 2019-09-12T18:14:11-07:00
List-Id: <comp.lang.ada>

I am not a proponent of OOP in general but I do think that some of the prin=
ciples of it can lead to better software.

I like the idea of defining how resources should be returned at the point w=
here they are acquired, but that does not define WHEN that should happen un=
less it is assumed that "going out of scope" is always the proper time.  Ad=
a is still a procedural language such that, outside of using Controlled typ=
es, one can read the lines of a sub-program and know the exact order of wha=
t is going to be executed.

My "inconvenience" is that there is no place in the syntax to execute code =
after the sub-program's main exception handler except to create a unfortuna=
te anonymous block only to provide that space following it.  Returning reso=
urces is only one example of a use-case for this syntax.  I think there are=
 other reasons this would be helpful.