Dan Sugalski <[EMAIL PROTECTED]> writes:
>At 01:17 PM 8/4/00 +0500, Tom Scola wrote:
>> >[I think this belongs on the language list, FWIW, Cc'd there]
>> >
>> >I like this, but I'd like to see this, inter-thread queues, and events
>>all
>> >use the same communication method. Overload filehandles to pass events
>>
>> >around instead, so:
>>
>>I'm proposing that events and threads be dropped in lieu of coroutines.
>
>Not gonna happen. Tk and signals, at the very least, will see to that.
As far as I am aware any multi-processing problem can be reduced to message
passing and these "co routines as IO" are just one stab at that.
For example occurance of a signal could just "print" down the handler "pipe",
Likewise mouse click could just "print" down the Tk-ish <ButtonPress-1> pipe.
It is the "return path" that bothers me - and of course the thread behind
the co routine still has locking issues if it updates "global" state.
--
Nick Ing-Simmons
