develooper Front page | perl.perl5.porters | Postings from August 2001

Re: Modules that get passed a bareword?

Thread Previous | Thread Next
Nick Ing-Simmons
August 20, 2001 01:06
Re: Modules that get passed a bareword?
Message ID:
Jeff Okamoto <> writes:
>> > I'm slowly working on some IPv6 stuff, and was trying to figure out if
>> > I can move connect/bind/accept (at least) out of Perl's core and into
>> > an XSUB module.
>> It is unclear to me why you need to change connect/bind/accept at all.
>> These functions were designed to be transport independent and does not
>> assume anything about IPv4.
>Unfortunately, they do.  Connect, bind, and accept all have arguments that
>must be different depending on the type of connection (sockaddr_un for
>AF_UNIX, sockaddr_in for AF_INET, and sockaddr_in6 for AF_INET6).

And we can already handle AF_UNIX and AF_INET with one connect,
which proves Gisle's point.

IMHO we leave AF_INET as IPv4 and add a new AF_INET6 (or whatever).

>> I thought all that was needed was a new module that formats the
>> address structs differently.  There is already a module on CPAN.
>> Can you explain?  Are there some extra RFC I should read that explains
>> this extra API you try to set up?
>I'll post a document that explains how I envision adding IPv6 functionality
>to Perl.
Nick Ing-Simmons

Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About