> 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: > > my $thing = <$handle>; > > could read a record from a file, or get an event from the event queue, or > receive some data from another thread. (With perhaps <$foo> in an lvalue > context being the same as sending a message down the filehandle to > whatever's on the other end) I have my way with the new open(), this'll happen. See RFC 14. Version 2 (which explores this in detail) should be up this afternoon. -Nate
- RFC 27 (v1) Coroutines for Perl Perl6 RFC Librarian
- Re: RFC 27 (v1) Coroutines for Perl Dan Sugalski
- Re: RFC 27 (v1) Coroutines for Perl Nathan Wiger
- Re: RFC 27 (v1) Coroutines for Perl Dan Sugalski
- Re: RFC 27 (v1) Coroutines for Perl Chaim Frenkel
- Re: RFC 27 (v1) Coroutines for Perl Michael Fowler
- Re: RFC 27 (v1) Coroutines for Perl Dan Sugalski
- Re: RFC 27 (v1) Coroutines for Perl Sam Tregar
- Re: RFC 27 (v1) Coroutines for Perl Tom Scola
- Re: RFC 27 (v1) Coroutines for Perl Dan Sugalski
- Re: RFC 27 (v1) Coroutines for Perl Uri Guttman
- Threaded Code Chaim Frenkel
- Re: RFC 27 (v1) Coroutines for Perl Nick Ing-Simmons