Making Coro::Socket Override IO::Socket::INET

jabowery has asked for the wisdom of the Perl Monks concerning the following question:

CPAN has a lot of modules for network access. While few of them are set up to support multithreading most use IO::Socket::INET. The cpan page for Coro::Socket says:

This module was written to imitate the IO::Socket::INET API

So an obvious question is:

Is there a better way to get networking modules that use IO::Socket::INET to instead use Coro::Socket, than to copy the code and do a search and replace?

Comment on Making Coro::Socket Override IO::Socket::INET

Replies are listed 'Best First'.
Re: Making Coro::Socket Override IO::Socket::INET by aitap (Curate) on Jun 17, 2013 at 18:14 UTC
You can probably acheive this by altering the symbol table: `package Bar; sub import { print "Hi!\n"; } package main; use warnings; use strict; BEGIN{{Foo::} = {Bar::};} # can't "use" there because there is no Foo.pm Foo::->import; __END__ Hi!` [download] Write a header in your script that once uses Coro::Socket and then replaces IO::Socket::INET:: namespace with Coro::Socket::. Subsequent uses of IO::Socket::INET will call import() from Coro::Socket and will use its subroutines. Edit: you'll probably need to use IO::Socket::INET before replacing namespaces, too, so further calls to it won't eval it and overwrite Coro::Socket's subs back.	[reply] [d/l]

Replies are listed 'Best First'.

Re: Making Coro::Socket Override IO::Socket::INET
by aitap (Curate) on Jun 17, 2013 at 18:14 UTC

package Bar;
sub import { print "Hi!\n"; }

package main;
use warnings;
use strict;

BEGIN{*{Foo::} = *{Bar::};}
# can't "use" there because there is no Foo.pm
Foo::->import;
__END__
Hi!
[download]

Write a header in your script that once uses Coro::Socket and then replaces IO::Socket::INET:: namespace with Coro::Socket::. Subsequent uses of IO::Socket::INET will call import() from Coro::Socket and will use its subroutines.

Edit: you'll probably need to use IO::Socket::INET before replacing namespaces, too, so further calls to it won't eval it and overwrite Coro::Socket's subs back.

[reply]
[d/l]