At 09:04 AM 8/4/00 -0700, Nathan Wiger wrote:
> > 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.
I don't know that overloading open is appropriate for this. There's no
reason that multiple different things return filehandles. It's a clever and
keyword-conserving hack to have open do a zillion different things, but it
might be better to have different creation/attachment methods for
conceptually distinct things.
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
