Nathan Wiger wrote:
> # Replaced by 'open socket'
> socket
> setsockopt # socket->options
> connect # overload <> or socket->connect
> shutdown # close instead
>
close and shutdown are not exactly the same, especially when a fork has
occurred and a child process may still be using the socket. this part of
the rfc may need to be changed as follows:
=head2 Syntax Changes
The C<open> function would have to be altered to accept this new syntax
and return a full-fledged B<fileobject>.
The C<close> function would need to be altered so it can accept some
modifiers, as is the case when you wish to close a socket.
close read $socket;
close write $socket;
close noshutdown $socket; # assuming close shutdown is the default.
C<close> will act on a B<fileobject> (or C<$_> if none is specified).
A method must be developed for registering classes as event handlers.
This has many more general applications than just for C<open>, and so
should be addressed in a separate RFC. For example, this process
>
> with handlers and open().
>
> Everyone: Before responding, please take a second to read the section
> called "Function Deletions" towards the bottom of
> http://dev.perl.org/rfc/14.pod, just so we don't have to rehash the same
> stuff here. Thanks.
>
> -Nate
--
___cliff [EMAIL PROTECTED]http://www.genwax.com/
