Tom Christiansen writes:
> >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!?!?

I vote for migration to a module.  If you're going to use the
long-winded form of socket diddling, you won't mind an extra
`use' statement at the top of your program.  Especially given that
you need to `use' a module to get constants and structs anyway
(although this too could be unstupided in the move to perl6).

Nat

Reply via email to