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. I'm not sure my idea would
accomplish that, hence the disclaimer. My point was just that if
IO::Socket was preventing us from possibly doing "really cool stuff", we
should fix it.

-Nate

Reply via email to