Coroutines were never intended to replace tasks, despite what wiki implies in the lead. See Conway, Melvin E. (July 1963). "Design of a Separable Transition-diagram Compiler" (PDF). Communications of the ACM. ACM. 6 (7): 396–408. doi:10.1145/366663.366704. at <http://melconway.com/Home/pdf/compiler.pdf>
________________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Paul Gilmartin <[email protected]> Sent: Sunday, July 16, 2023 12:17 PM To: [email protected] Subject: Re: C++ coroutines are recent, and difficult? On Sun, 16 Jul 2023 11:08:51 +0000, 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 qualités. At times one wants things to run concurrently yet share storage, locking only when necessary for integrity. Even with only one CPU locking is sometimes necessary because of preemptive dispatching. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
