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=-0.3 required=5.0 tests=BAYES_00,
	REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: "G.B." <bauhaus@futureapps.invalid>
Newsgroups: comp.lang.ada
Subject: Re: tasks as part of record
Date: Mon, 06 Oct 2014 13:40:29 +0200
Organization: A noiseless patient Spider
Message-ID: <m0tv3b$tjv$1@dont-email.me>
References: <294a973f-5222-4aa3-8971-777cd2eb9174@googlegroups.com>
 <c9ccpaF6mooU1@mid.individual.net>
 <c474fef2-701c-4968-94eb-aec57bee0dd3@googlegroups.com>
 <c9eu13Fqo1jU1@mid.individual.net>
 <1ek4634mtnybu.2yqt65o532me$.dlg@40tude.net>
Reply-To: nonlegitur@futureapps.de
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Mon, 6 Oct 2014 11:40:27 +0000 (UTC)
Injection-Info: mx05.eternal-september.org;
 posting-host="b96887e80893c84a90c3007226ca0d1c";
	logging-data="30335"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX193BOpuJaui8Ml6VcbV2mK1WJUUJMj6eEA="
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
 rv:24.0) Gecko/20100101 Thunderbird/24.6.0
In-Reply-To: <1ek4634mtnybu.2yqt65o532me$.dlg@40tude.net>
Cancel-Lock: sha1:AuBEcSSUVxN+RgGO+mDtyN6QqZA=
Xref: news.eternal-september.org comp.lang.ada:22141
Date: 2014-10-06T13:40:29+02:00
List-Id: <comp.lang.ada>

On 06.10.14 10:00, Dmitry A. Kazakov wrote:

> 1. Separate record and task one referencing another;
> 2. Task in a limited record with an access discriminant to;
> 3. Data hidden in the task, exposed via task's entry.
>
> #1 is a mess;
>
> #2 is active object and has issues with initialization/finalization and
> most likely will break under inheritance;
>
> #3 is heavy-weight and coarse because all interfacing go though entries,
> entries may have no results, tasks are non-tagged.

#4 could be a pattern as is used in Paraffin, I think:
submit student jobs to some task pool, where "job" describes,
in terms of Ada, a way of executing jobs.