Re^5: importing functions with "PerlModule" Apache directive

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'

Comment on Re^5: importing functions with "PerlModule" Apache directive Select or Download Code

Replies are listed 'Best First'.
Re^6: importing functions with "PerlModule" Apache directive by Anonymous Monk on May 09, 2012 at 14:06 UTC
:) but but but but but but but but acanfora says that Vars() is available :P	[reply]
Re^6: importing functions with "PerlModule" Apache directive by acanfora (Novice) on May 09, 2012 at 14:44 UTC
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]