From: "G.B." <bauhaus@futureapps.invalid>
Subject: Re: tasks as part of record
Date: Mon, 06 Oct 2014 13:40:29 +0200
Date: 2014-10-06T13:40:29+02:00 [thread overview]
Message-ID: <m0tv3b$tjv$1@dont-email.me> (raw)
In-Reply-To: <1ek4634mtnybu.2yqt65o532me$.dlg@40tude.net>
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.
next prev parent reply other threads:[~2014-10-06 11:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-04 13:11 tasks as part of record Stribor40
2014-10-04 13:33 ` Simon Wright
2014-10-04 22:12 ` Stribor40
2014-10-05 7:36 ` Jacob Sparre Andersen
2014-10-05 8:11 ` Niklas Holsti
2014-10-06 3:47 ` Stribor40
2014-10-06 5:43 ` Jeffrey Carter
2014-10-06 7:18 ` Niklas Holsti
2014-10-06 8:00 ` Dmitry A. Kazakov
2014-10-06 11:40 ` G.B. [this message]
2014-10-06 8:06 ` Simon Wright
2014-10-06 8:24 ` Simon Wright
2014-10-12 22:33 ` compguy45
2014-10-13 7:32 ` Simon Wright
2014-10-13 14:45 ` compguy45
2014-10-13 15:33 ` Shark8
2014-10-18 18:21 ` Stephen Leake
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox