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.7 required=5.0 tests=BAYES_00,INVALID_DATE,
	MSGID_SHORT,REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no
	version=3.4.4
Path: utzoo!mnetor!uunet!husc6!hao!boulder!sunybcs!moogvax!terry
From: terry@moogvax.UUCP (Terry Westley)
Newsgroups: comp.lang.ada
Subject: Re: INFO-ADA Digest V88 #47
Message-ID: <709@moogvax.UUCP>
Date: 10 Mar 88 13:28:25 GMT
References: <8802202149.AA07429@ajpo.sei.cmu.edu> <415@zap.UUCP> <17701@think.UUCP>
Reply-To: terry@moogvax.UUCP (Terry Westley)
Organization: Moog Inc. Electronics & Systems Division, Orchard Park NY
Keywords: INITIATE
Summary: What is INITIATE?
List-Id: <comp.lang.ada>

In article <17701@think.UUCP> barmar@fafnir.think.com.UUCP (Barry Margolin) writes:
>In a non-preemptive environment, there wouldn't be any notion of "time
>slice".  A task returns control to the scheduler any time it executes
>a DELAY, ACCEPT, SELECT, or INITIATE statement, or when it calls a
>task entry.

I know about DELAY, ACCEPT, SELECT, and entry calls, but what is an 
INITIATE statement?
-- 
  Terry Westley         
  Moog, Inc. (no, not the synthesizer company)
  East Aurora, NY  14052-0018
  {boulder,decvax,rocksanne,rutgers,ames}!sunybcs!moogvax!terry