|Syntactic Confectionery Delight|
Re^2: global varby tultalk (Monk)
|on Apr 05, 2017 at 20:51 UTC||Need Help??|
Hi: Did not want to post tooooo much.
A good readHow to Import In other files which wish to use your module there are three basic ways for them to load your module and import its symbols: use YourModule; This imports all the symbols from YourModule's @EXPORT into the namespace of the use statement. use YourModule (); This causes perl to load your module but does not import any symbols. use YourModule qw(...); This imports only the symbols listed by the caller into their namespace. All listed symbols must be in your @EXPORT or @EXPORT_OK , else an error occurs. The advanced export features of Exporter are accessed like this, but with list entries that are syntactically distinct from symbol names.
I assume you recommend @EXPORT_OK and YourModule qw(...);
Having clarified the code, is there anything you can see that would prevent my grabbing $userid_1 correctly?
Now in reading this:
When using Exporter with the standard strict and warnings pragmas, the our keyword is needed to declare the package variables @EXPORT_OK , @EXPORT , @ISA , etc.
So now my function calls that used to work: Undefined subroutine &main::ProcessLoginRequest called at manage_users.cgi line 86.
So now I have to change all these calls to $manageusers::ProcessLoginRequest. Is that correct? Or change use manageusers; to use manageusers qw(myimportlist);
I guess posting too much is better than posting too little.