import conundrum
- From: kj <socyl@xxxxxxxxxxxxxxxxx>
- Date: Thu, 29 Mar 2007 22:18:01 +0000 (UTC)
According to the documentation for "use", if one wants to prevent
a module's import from being called when the module is use'd, one
is supposed pass an empty list as the second argument to "use":
use Foo::Bar ();
But now suppose that Foo::Bar in turn use's some other module Foo:
############################################################
# Foo/Bar.pm
package Foo::Bar;
use Foo;
# yadda-yadda
1;
__END__
############################################################
and, furthermore, suppose that Foo *has* an import method:
############################################################
# Foo.pm
package Foo;
sub import {
shift->go_nuts( @_ );
}
# yadda-yadda
1;
__END__
############################################################
In this case, even if the user loads Foo/Bar.pm with "use Foo::Bar
()", Foo::import is still invoked.
My problem is this: how to give the users of Foo::Bar the opportunity
to veto the calling of Foo::import? The only approach I can think
of is to define a Foo::Bar::import method whose only function is
to call Foo::import, and change the line "use Foo" to "use Foo ()":
############################################################
# Bar/Foo.pm
package Foo::Bar;
use Foo ();
sub import {
shift;
Foo->import( @_ );
}
# yadda-yadda
1;
__END__
############################################################
This does indeed have the effect of "transmitting" the "()" argument
from "use Foo::Bar ()" through to Foo. But in a suite of modules
of any complexity this approach quickly becomes cumbersome.
Is there any other for Foo to know that it has been use'd by a
module that *itself* was use'd with a "()" argument?
TIA!
kj
--
NOTE: In my address everything before the first period is backwards;
and the last period, and everything after it, should be discarded.
.
- Follow-Ups:
- Re: import conundrum
- From: Christian Winter
- Re: import conundrum
- Prev by Date: Re: HowTo parse huge Files
- Next by Date: Re: What are OOP's Jargons and Complexities
- Previous by thread: LWP::UserAgent and HTTP::Request with basic authentication...
- Next by thread: Re: import conundrum
- Index(es):
Relevant Pages
|
|
