On Fri, Mar 03, 2006 at 05:54:43PM -0600, Joshua Isom wrote: > I don't think it's really been addressed, at least not recently, but > what about IPv6? By the time perl6 becomes commonplace and used > often(and thus, parrot), IPv6 will be common enough that problems could > occur. Currently it's not speced or stated, aside from a comment in > PIO_sockaddr_in.
The draft has: =item * C<sockaddr> returns a string representing a socket address, generated from a port number (integer) and an address (string). I don't think that this is appropriate. It's IPv4 specific. It doesn't cover AF_UNIX (er, AF_LOCAL), IPv6, or any of the other address formats (of which I'm not sure if any other than IPX are still commonly used. I'm not sure how to make an appropriate interface, partly as I have little idea if it's possible to make a sufficiently flexible abstraction for address names. IPv4 and IPv6 both use addresses and port numbers. AF_LOCAL just uses a string, which is a file system path. But I think that specifying an op for just one address format is too narrow. Nicholas Clark
