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: 
 border1.nntp.ams3.giganews.com!border2.nntp.ams3.giganews.com!border2.nntp.ams2.giganews.com!border4.nntp.ams.giganews.com!border2.nntp.ams.giganews.com!nntp.giganews.com!newsfeed.tele2net.at!aioe.org!.POSTED!not-for-mail
From: "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>
Newsgroups: comp.lang.ada
Subject: Re: Ada advocacy
Date: Thu, 29 Aug 2013 09:15:21 +0200
Organization: cbb software GmbH
Message-ID: <1f7k3ggkq33l6.1vlb4iq12hvyd$.dlg@40tude.net>
References: <vhcvr8d4kq6ribdqeeb0b857ei5aa5luiv@4ax.com>
 <6c58fae4-6c34-4d7a-ab71-e857e55897c0@x6g2000vbj.googlegroups.com>
 <wccvc5b49yc.fsf@shell01.TheWorld.com> <op.w2g9br0kule2fv@cardamome>
 <246849b7-7a53-48a2-8f64-ff6dfb2086ce@googlegroups.com>
 <521dbbbb$0$9520$9b4e6d93@newsspool1.arcor-online.net>
 <1spiuuuxfwqq4$.46v46qs98684.dlg@40tude.net>
 <521de20d$0$9507$9b4e6d93@newsspool1.arcor-online.net>
 <op.w2jcso19ule2fv@cardamome> <1ko98ye6q8bzv.134llfoupp81w.dlg@40tude.net>
 <v12t19tej4h7lcu7mh0084dmdnaa0mfue0@4ax.com>
Reply-To: mailbox@dmitry-kazakov.de
NNTP-Posting-Host: IenaDxMXK2hi7fvYcb+MlQ.user.speranza.aioe.org
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Complaints-To: abuse@aioe.org
User-Agent: 40tude_Dialog/2.0.15.1
X-Notice: Filtered by postfilter v. 0.8.2
X-Original-Bytes: 2357
Date: 2013-08-29T09:15:21+02:00
List-Id: <comp.lang.ada>

On Wed, 28 Aug 2013 19:33:23 -0400, Dennis Lee Bieber wrote:

> On Wed, 28 Aug 2013 19:25:59 +0200, "Dmitry A. Kazakov"
> <mailbox@dmitry-kazakov.de> declaimed the following:
> 
>>Maybe instead of coroutines... Ada does not specify whether tasks should be
>>native. What about providing tasks scheduled by the RTL (or user), in
>>addition to the native tasks, not as a replacement. Such tasks would have
> 
> 	Of course, that implies that those tasks have no CPU time if their
> parent task/scheduler is suspended or blocked. It is the return of Windows
> 3 <G>

Yes, MS-DOS INT 13, if I correctly remember the number.

The main (only?) use case for co-routines is programming event-driven state
machines as if the I/O were blocking and not an asynchronous one
(completion event). E.g. socket-select stuff. GUI programming could also
use them is some cases (when the user must click through a sequence (tree)
of controls).

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de