Think generators and iterators.
From: IBM Mainframe Discussion List on behalf of
Rupert Reynolds
Sent: Sunday, July 16, 2023 2:03 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: C++ coroutines are recent, and difficult?
Oh I see!
Thanks. Yes, that would
on List [IBM-MAIN@LISTSERV.UA.EDU] on behalf
> of Rupert Reynolds [rreyno...@cix.co.uk]
> Sent: Sunday, July 16, 2023 6:01 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: C++ coroutines are recent, and difficult?
>
> I must have missed the point of something, because on first reading, it
.com/Home/pdf/compiler.pdf>
From: IBM Mainframe Discussion List on behalf of
Paul Gilmartin <042bfe9c879d-dmarc-requ...@listserv.ua.edu>
Sent: Sunday, July 16, 2023 12:17 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: C++ coroutines are recent,
On Sun, 16 Jul 2023 11:08:51 +, Seymour J Metz wrote:
>With ATTACH, you need to play games to prevent two tasks from running
>concurrently on two CPUs. With coroutines, you have multiples contexts within
>a single thread; there is no need for explicit interlocking.
>
Il a les défauts de ses
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Rupert Reynolds [rreyno...@cix.co.uk]
Sent: Sunday, July 16, 2023 6:01 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: C++ coroutines are recent, and difficult?
I must have missed the point of something, because
I must have missed the point of something, because on first reading, it's
analogous to what we could do with ATTACH, ECB and WAIT in assembly under
z/OS and MVS, or the equivalents in PL/I and COBOL (I assume) where we have
a subtask which can wait for an event and then resume operation from its
