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 X-Received: by 10.28.45.208 with SMTP id t199mr543588wmt.0.1466267238313; Sat, 18 Jun 2016 09:27:18 -0700 (PDT) X-Received: by 10.157.34.202 with SMTP id y68mr261296ota.4.1466267238198; Sat, 18 Jun 2016 09:27:18 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!feeder.eternal-september.org!goblin1!goblin.stu.neva.ru!w10no2341066lbo.0!news-out.google.com!di11ni24868lbb.1!nntp.google.com!oe3no4142088lbb.1!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Sat, 18 Jun 2016 09:27:18 -0700 (PDT) In-Reply-To: <98d70020-a1cd-426d-9531-6edd070ab869@googlegroups.com> Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=72.173.184.4; posting-account=uInPWgoAAAD9VvUJDc0jNwDhBg_137JZ NNTP-Posting-Host: 72.173.184.4 References: <58b78af5-28d8-4029-8804-598b2b63013c@googlegroups.com> <98d70020-a1cd-426d-9531-6edd070ab869@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <3775db87-5706-4aa5-bef3-3c32f657b0e4@googlegroups.com> Subject: Re: RFC: Prototype for a user threading library in Ada From: "Jeffrey R. Carter" Injection-Date: Sat, 18 Jun 2016 16:27:18 +0000 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Xref: news.eternal-september.org comp.lang.ada:30785 Date: 2016-06-18T09:27:18-07:00 List-Id: On Saturday, June 18, 2016 at 4:38:34 AM UTC-7, Hadrien Grasland wrote: > After going through a thesaurus a bit, what would you think about "job", = perhaps with an extra "asynchronous" qualifier? >=20 > The term has a long history of being used in various task scheduling cont= exts. A minor issue is that it tends to be associated with batch processing= , but that is not an extremely strong connection, and isn't entirely wrong = either. In general, the term reflects the idea of an ongoing process withou= t abusing that specific word. I think it could work quite well. Yes. Since yesterday (see my post on Eternal September) I've been trying to= post: Although your terminology is different, IIUC, this seems to be library to p= rovide job pools: a set of tasks that can process jobs as they become avail= able. A job, which you confusingly call an asynchronous task, is defined by= a type with an associated operation. A task (in Ada terms) in the pool sim= ply obtains a value of the type and invokes the operation on it. The librar= y provides queuing for jobs when all tasks are busy, blocking of tasks when= no jobs are available, and the creation of the tasks. There is a number of= variations of the problem, mostly depending on dynamic/static creation of = tasks and whether/how tasks terminate.