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=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: 103376,8e11100f675ea2df,start
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
X-Received: by 10.66.74.135 with SMTP id t7mr5357797pav.29.1356913310931;
        Sun, 30 Dec 2012 16:21:50 -0800 (PST)
Path: 
 s9ni73446pbb.0!nntp.google.com!Xl.tags.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local2.nntp.dca.giganews.com!nntp.earthlink.com!news.earthlink.com.POSTED!not-for-mail
NNTP-Posting-Date: Sun, 30 Dec 2012 18:21:50 -0600
Date: Sun, 30 Dec 2012 16:16:19 -0800
From: Charles Hixson <charleshixsn@earthlink.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:10.0.11) Gecko/20121122 Icedove/10.0.11
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Subject: asynchronous task communication
Message-ID: <1c2dnd5E6PMDR33NnZ2dnUVZ_sednZ2d@earthlink.com>
X-Usenet-Provider: http://www.giganews.com
NNTP-Posting-Host: 216.244.16.210
X-Trace: 
 sv3-Cswozfcf1+Ge82Bq4CPAIQbTxQWAJiTsUOmdQyL1oJCxIQ9Y4FZ7WdG0YIQjtGs/IXGUV+m7k1f9xaL!lyaQGtECl6l4rSJxgrKWjGXjo04c3VuKOYLMEV8aN9nmBJ+Vjl7fIXsljmFff2zbpD5DySfZb6oo!v7DYXsolxGMg+PRCwDnCXg==
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint
 properly
X-Postfilter: 1.3.40
X-Original-Bytes: 1982
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Date: 2012-12-30T16:16:19-08:00
List-Id: <comp.lang.ada>

Is it possible to call an entry point of a task from another task and 
not wait for the task to finish?
I'm thinking of an entry point that would have only _in_ parameters, and 
which is not expected to fail, but the thread called might be busy, so 
I'd like to just queue it and go on to something else.  This doesn't 
appear to be what an "asynchronous select" does, though I'll admit I'm 
not sure, as I can't tell why they call it asynchronous...timed seems 
more reasonable than asynchronous,

What I'm after is sort of like sending a letter from one task to 
another.  The sender doesn't need to wait for the receiver to accept the 
message (though, ideally, there would also be a "return receipt 
requested" option).

The only alternative that I've come up with is to have each task have an 
access variable to a protected type instance.  This can be done, but it 
makes the control in other parts of the program trickier.