in reply to Re: Re: mod_perl and modules (Or "how do I import subs into my PerlHandler module)
in thread mod_perl and modules (Or "how do I import subs into my PerlHandler module)

Hum.
Well usually everything in @EXPORT is exported by default when under normal use, and only stuff in EXPORT_OOK has to be exported explicitely.
Apparently (from my experience, but I might do something wrong) under mod_perl, you'd better import everything explicitely else it won't work.
  • Comment on Re: Re: Re: mod_perl and modules (Or "how do I import subs into my PerlHandler module)

Replies are listed 'Best First'.
Re: Re: Re: Re: mod_perl and modules (Or "how do I import subs into my PerlHandler module)
by perrin (Chancellor) on Nov 22, 2002 at 15:46 UTC
    mod_perl should not affect the behavior of the exporter. I think there must be something else going on.
[reply]
      Hum, I'm sorry but mod_pel does (?)fiddle with the exporter. It puts all modules under the name Apache::something for example.
[reply]
        No, it doesn't. A PerlHandler module will be in whatever package you declare. Apache::Registry generates package names for CGI scripts, but even then it doesn't affect the exporter. See this section on sharing variables with the exporter, for example.
[reply]

In Section Seekers of Perl Wisdom