Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.csd.uwm.edu!gem.mps.ohio-state.edu!ginosko!uunet!ficc!peter
From: peter@ficc.uu.net (Peter da Silva)
Newsgroups: comp.lang.c
Subject: Re: Coroutines in C
Message-ID: <5773@ficc.uu.net>
Date: 18 Aug 89 13:02:34 GMT
References: <5663@ficc.uu.net> <2151@netcom.UUCP>
Organization: Xenix Support, FICC
Lines: 21

In article <2151@netcom.UUCP>, hinton@netcom.UUCP (Greg Hinton) writes:
> In article <5663@ficc.uu.net> peter@ficc.uu.net (Peter da Silva) writes:
> >Isn't it about time that there was some effort made to provide a standard
> >coroutine library in C.
> >These routines together would allow the portable implementation of threads
> >on a wide variety of systems, if they became widespread.

> Isn't this precisely what the language Concurrent C attempts?

Concurrent C is a different language. I can't take a couple of pages
of code and use them to implement threads for a C compiler and library
I don't have the source to. In many C compilers I wouldn't even need
to write any assembly code, since setjmp/longjmp can be used to implement
the context switch.

This is not nearly as ambitious a project as Concurrent C.
-- 
Peter da Silva, *NIX support guy @ Ferranti International Controls Corporation.
Biz: peter@ficc.uu.net, +1 713 274 5180. Fun: peter@sugar.hackercorp.com. `-_-'
"Optimization is not some mystical state of grace, it is an intricate act   U
   of human labor which carries real costs and real risks." -- Tom Neff