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:a24:b250:: with SMTP id
 h16-v6mr772798iti.19.1538059428275;
        Thu, 27 Sep 2018 07:43:48 -0700 (PDT)
X-Received: by 2002:a9d:618e:: with SMTP id g14-v6mr158014otk.3.1538059428200;
 Thu, 27 Sep 2018 07:43:48 -0700 (PDT)
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!news.gegeweb.eu!gegeweb.org!usenet-fr.net!proxad.net!feeder1-2.proxad.net!209.85.166.216.MISMATCH!x98-v6no65566ita.0!news-out.google.com!z5-v6ni74ite.0!nntp.google.com!x98-v6no65565ita.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Thu, 27 Sep 2018 07:43:47 -0700 (PDT)
In-Reply-To: <0956f152-7902-47cb-98e2-c6e5ba68b6b5@googlegroups.com>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=146.5.17.88;
 posting-account=lJ3JNwoAAAAQfH3VV9vttJLkThaxtTfC
NNTP-Posting-Host: 146.5.17.88
References: <0956f152-7902-47cb-98e2-c6e5ba68b6b5@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <6632bf33-17aa-46f8-9ef7-f6e025eab3a4@googlegroups.com>
Subject: Re: Code organization
From: Shark8 <onewingedshark@gmail.com>
Injection-Date: Thu, 27 Sep 2018 14:43:48 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Xref: reader02.eternal-september.org comp.lang.ada:54440
Date: 2018-09-27T07:43:47-07:00
List-Id: <comp.lang.ada>

On Thursday, September 27, 2018 at 8:24:48 AM UTC-6, NiGHTS wrote:
>=20
> Any thoughts on this?

Organizationally, I've been able to leverage SEPARATE and nested packages t=
o a fairly decent effect.

As for the particular problem of the nested-task I don't think that would w=
ork, although you /could/ make a generic package off of that internal task,=
 using IN OUT formal parameters for the dependent state you're relying on..=
. though I'm not sure that would make things easier, per se.