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

Pay attention: I stated that Vars is actually available in my test script even if I did not imported it (purposely, at least) in any way.
startup.pl script:

use CGI;

mytestscript:

#!/usr/bin/perl
local our $p=Vars; # it works!!!

[download]

Replies are listed 'Best First'.
Re^5: importing functions with "PerlModule" Apache directive
by tobyink (Canon) on May 09, 2012 at 14:03 UTC

    You're not using strict, so of course local our $p=Vars will work. It's just an assignment of a string to a package variable. Compare:

    $ perl -ce'local our $p=Vars'
-e syntax OK

    [download]

    versus:

    $ perl -Mstrict -ce'local our $p=Vars'
Bareword "Vars" not allowed while "strict subs" in use at -e line 1.
-e had compilation errors.

    [download]

    Also of interest:

    $ perl -MO=Deparse -e'local our $p=Vars'
local $p = 'Vars';
-e syntax OK

    [download]
    perl -E'sub Monkey::do{say$_,for@_,do{($monkey=[caller(0)]->[3])=~s{::}{ }and$monkey}}"Monkey say"->Monkey::do'
[reply]
[d/l]
[select]

      :) but but but but but but but but acanfora says that Vars() is available :P

[reply]
      My question is not about barewords. I can use Vars or Vars(), no matter what, my point is not that. The point is about _visibility_ of _function_ Vars in script _whithout_ pass through CGI object instantiation and _whithout_ explicitly importing anything via qw(whatever). Sorry for my bad English.
[reply]
Re^5: importing functions with "PerlModule" Apache directive
by Anonymous Monk on May 09, 2012 at 13:17 UTC
[reply]
      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]

In Section Seekers of Perl Wisdom