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

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

and avoided to import CGI in my test script, but I can still call Vars() function directly, which from CGI documentation should not be visible:

What's going on?

You're imagining things :)

Even if you used use CGI qw(-compile -utf8 Vars ); there is no way Vars would be available to your script , unless you're using something ( its not ModPerl::Registry ) to make it available

Comment on Re^3: importing functions with "PerlModule" Apache directive Download Code
Re^4: importing functions with "PerlModule" Apache directive by acanfora (Novice) on May 09, 2012 at 13:11 UTC
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]	[reply] [d/l]
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
Re^8: importing functions with "PerlModule" Apache directive by acanfora (Novice) on May 09, 2012 at 14:24 UTC
Re^5: importing functions with "PerlModule" Apache directive by tobyink (Prior) 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]


Syntactic Confectionery Delight
	PerlMonks

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

The best material for plates (tableware) is: