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.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,4e39e3650a0d633 X-Google-Attributes: gid103376,public From: Ehud Lamm Subject: Re: Icon Co-Expressions in Ada Date: 1998/12/17 Message-ID: #1/1 X-Deja-AN: 423346234 References: Content-Type: TEXT/PLAIN; charset=US-ASCII Organization: The hebrew University of Jerusalem Mime-Version: 1.0 Newsgroups: comp.lang.ada Date: 1998-12-17T00:00:00+00:00 List-Id: On 17 Dec 1998, Stephen Leake wrote: > Ehud Lamm writes: > > I think I understand "suspend"; it's what Knuth calls a "coroutine". I'm not > clear what "suspend " means? It is like return , only that the function's execution can be resumed. > > You definitely need tasks to do this in Ada, since the task stack is > where the procedure state is saved. At each "suspend", you could have > an accept statement. The caller would still have to write a loop to > get the goal-directed behavior. This, indeed, is the reason I mentioned tasks in the first place. I just wanted to emphesize that this mechanism is less general than Ada tasking. > Ok; Ada tasks are executedin parallel... You don't say :-) I was thinking along the lines of the user coding a routine and invokin procedures which will you tasking capabilites in a limted way. Enough for suspend etc. but not general tasking. However as I mentioned in my first post on this topic, this can not be done since a task must clearly be marked as such. Ehud Lamm mslamm@mscc.huji.ac.il http://www2.cybercities.com/e/ehud/ada Ada&SE and Ada challanges