Chaim Frenkel wrote:
>
> You forget that open() handles all the magic. "| ...", " ...|", and
> the rest of the family. Sysopen specifically doesn't. So one could
> easily (and does) use open to do the magic, and then uses sysread/syswrite
> to handle the dirty details of playing with a pipe.
Yeah, I agree. Unless there's any objections, for the moment I'm going
to take the socket stuff and the sysopen stuff out of the main part of
the RFC and list it under a "possible extensions" section.
The more I've looked at sysopen(), the more it looks like pipe() than
open() to me. Same with socket(). Filehandle-returning or not. However,
I would recommend that anything returning a fileobject should use the
new open() syntax:
$socket = socket ...
$file = sysopen ...
However, open() shouldn't be the replacement for every operator in Perl.
:-) I think making it an extensible and fileobject-oriented version of
what's there is a good enough improvement.
-Nate
