Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!lavaca.uh.edu!menudo.uh.edu!sugar!peter From: peter@sugar.hackercorp.com (Peter da Silva) Newsgroups: comp.sys.amiga.misc Subject: Re: Multitasking Definitions (Was: True Multitasking) Message-ID: <7641@sugar.hackercorp.com> Date: 28 Jan 91 12:38:02 GMT References: <1991Jan18.055614.13889@zorch.SF-Bay.ORG> <42149@nigel.ee.udel.edu> <15750@sdcc6.ucsd.edu> Reply-To: peter@sugar.hackercorp.com (Peter da Silva) Organization: Sugar Land Unix - Houston Lines: 15 In article mwm@raven.relay.pa.dec.com (Mike (My Watch Has Windows) Meyer) writes: > [CRs take] responsibility for saving whatever state it needs to restart. What state is this? A coroutine's state is just its stack, and that's saved by the co-call. > Further, if you're willing to do the appropriate magic, you can get > LWPs without OS support specifically for them; but it's a lot of fuss. All you need is the ability to set up a stack context, and switch to another stack. Then add a round-robin scheduler. It's not a *lot* of fuss but it does tend to be machine, compiler, and even compiler revision dependent. -- Peter da Silva. `-_-' .