Re: Re: Re: How do I make one package use a module from another package?

Hi jryan,

What about doing this?:

package whatever;
require Exporter;
use anything;
push(@EXPORT, @anything::EXPORT);
[download]

I got this snippet from the source of LWP::Simple. I am not sure what is going on, but it worked. But I can't export strict for some reason. I could export other modules like diagnostics. What is going on here? And is your way better? Thanks.

Comment on Re: Re: Re: How do I make one package use a module from another package? Download Code

Replies are listed 'Best First'.
Re: Re: Re: Re: How do I make one package use a module from another package? by jryan (Vicar) on Jul 23, 2003 at 03:06 UTC
I think you are seeing different behaivor than you think you are. The above code looks like it might be used to, for lack of a better term, "functionally subclass" a module. By that, I mean that the "subclass" exports everything that the "base class" does, in addition to its own exports. For instance, in the LWP::Simple module, the "use anything;" in question happens to be "use Http::Status". `Http::Status` happens to have a huge list of default Exports, so the author uses the above code in order to save his code from repetition. (which is A Bad Thing) As for the behaivor that you think you are seeing, the problem is that `diagnostics` isn't lexical like `strict` is. It operates as a global switch; either `diagnostics` is on or it isn't. (You can use the kludgy `enable` and `disable` to acheive lexical behaivor). However, strict is lexical, which is why nothing happend. (Besides, `diagnostics` mostly operates at runtime, and `strict 'vars'` operates at compile time. By the time the above code is run, it is already runtime, and so it would be tough for `strict 'vars'` to have an effect (-: ) So, in short; yes, my solution is "way better." (-:	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re: Re: Re: Re: How do I make one package use a module from another package?
by jryan (Vicar) on Jul 23, 2003 at 03:06 UTC

I think you are seeing different behaivor than you think you are. The above code looks like it might be used to, for lack of a better term, "functionally subclass" a module. By that, I mean that the "subclass" exports everything that the "base class" does, in addition to its own exports. For instance, in the LWP::Simple module, the "use anything;" in question happens to be "use Http::Status". Http::Status happens to have a huge list of default Exports, so the author uses the above code in order to save his code from repetition. (which is A Bad Thing)

As for the behaivor that you think you are seeing, the problem is that diagnostics isn't lexical like strict is. It operates as a global switch; either diagnostics is on or it isn't. (You can use the kludgy enable and disable to acheive lexical behaivor). However, strict is lexical, which is why nothing happend. (Besides, diagnostics mostly operates at runtime, and strict 'vars' operates at compile time. By the time the above code is run, it is already runtime, and so it would be tough for strict 'vars' to have an effect (-: )

So, in short; yes, my solution is "way better." (-:

[reply]
[d/l]
[select]