in reply to Re^4: importing functions with "PerlModule" Apache directive
in thread importing functions with "PerlModule" Apache directive

Pay attention: ...

I did, what makes you think I didn't?

On the other hand, you haven't mentioned how you're running your "script", ModPerl::Registry or what?

See How do I post a question effectively?, Corion on reproducibility, how to report-a-bug, not to ask a question, ask question effectively

  • Comment on Re^5: importing functions with "PerlModule" Apache directive

Replies are listed 'Best First'.
Re^6: importing functions with "PerlModule" Apache directive
by acanfora (Novice) on May 09, 2012 at 13:38 UTC
    I am using Registry. I also found (it seems) the reason of the weird behavior: the CGI module makes use of AUTOLOAD. I think Apache::Request should be more suited to my purposes in this case...
[reply]

      I also found (it seems) the reason of the weird behavior: the CGI module makes use of AUTOLOAD.

      Nope, AUTOLOAD doesn't have anything to do with exporting

      And since Registry compiles your program into its own namespace, there is no way exporting stuff (which you don't do) in startup.pl into namespace main would affect the custom Registry namespace your program is compiled in

      Are you using unmodified CGI.pm? Which version?

[reply]
        CGI is 3.59, unmodified, of course :)
[reply]

In Section Seekers of Perl Wisdom