>Tom Christiansen wrote:
>> 
>> >> Thats just because IO::Socket is done wrong
>> 
>> >Maybe we should address this? If we're keeping syscalls just because a
>> >possible replacement module is just written wrong, we should fix this.
>> 
>> Why would we ever remove a syscall!?!?

>Sorry, wrong verbage. I meant "the general purpose socket()". And even
>then, no, I'm *not* in favor of removing it. At all. Just maybe changing
>it to make it better, faster, more portable. 

Better and faster are good; you'll note that the socket-related
syscalls in Perl are already somewhat different from those of libc,
so it's as though diddling them in a perlian way weren't par for
this course.   So go right ahead.

However, I'm not sure what "more portable" has to do with anything.

--tom

Reply via email to