Michael Peters wrote:
Scott Serr wrote:
I've read those and unfortunately they didn't help me. (I'm not a
Perl programmer, but that's probably not an excuse.)
Separate from Inline, Exporter seems like a way to expose module
symbols to the caller.
I hope I'm not stating the obvious here, but anything you pass to a
"use" statement in addition to the module name get's passed into that
module's import() sub. Exporter just makes this easy by giving you
some vars to play with and it's own import() sub.
Ditch Exporter and write your own import() sub to take the list that
you want and pass it to Inline::Java's import() sub. Something like this:
package BOB;
use Inline::Java;
sub import {
my $class = shift;
Inline::Java->import(@_);
}
I think you stated what I obviously should have known. THANK YOU! I
had even tried looking at @_, but didn't understand that I could make my
own import() sub.
