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

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]
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]
Re^5: importing functions with "PerlModule" Apache directive by Anonymous Monk on May 09, 2012 at 13:17 UTC
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	[reply]
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]
Re^7: importing functions with "PerlModule" Apache directive by Anonymous Monk on May 09, 2012 at 13:53 UTC
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]
Re^8: importing functions with "PerlModule" Apache directive by acanfora (Novice) on May 09, 2012 at 14:24 UTC


Just another Perl shrine
	PerlMonks