Re: global var

Replies are listed 'Best First'.
Re^2: global var by tultalk (Monk) on Apr 05, 2017 at 20:51 UTC
Hi: Did not want to post tooooo much. package manageusers; use strict; use diagnostics -verbose; use warnings; use CGI; #use Carp::Always; use CGI::Carp qw(fatalsToBrowser warningsToBrowser); use CGI qw(:standard escapeHTML); use CGI qw/:standard/; use Data::Dumper; use Digest::MD5 qw(md5_hex); #use DB_File; # persistent hash database use CGI::Session; use CGI::Cookie; #use vars qw($session_cookie1 $session_cookie2 $login_timeout); #use vars qw($session); use Mail::Sendmail; use Time::HiRes qw(usleep); use Time::Local; BEGIN { use vars qw($VERSION @ISA @EXPORT); use DBI; # $ENV{DBI_TRACE}=1; # $ENV{PERL_DBI_DEBUG}=1; require Exporter; @ISA = qw(Exporter); # exported functions @EXPORT = qw( &OpenConnection &OpenSession &ProcessLoginRequest &ProcessLostDataRequest &LoginUser &decodeEncryptedPassName &UpdateUserData &GetUserLostData &LogoutUser &GetUserSessionCookie &CheckForAuthorizedUser &Expires $attempts $adminaccess $LoggedOn_user_id &Now &CheckValidLoginChar &CheckValidEmailChar &print_md5_javascript); $VERSION = '0.0.1'; } [download] A good read How 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.	[reply] [d/l]
Re^3: global var by stevieb (Canon) on Apr 05, 2017 at 21:01 UTC
See GotToBTru's post to create a proper example, but from your code, I see this: `# exported functions` [download] That makes me think you copy/pasted something off of the Internet, and with the lines that follow that comment, it appears it closely resembles perl4 code (or someone coding perl5 that hasn't migrated to the perl5 mindset yet. This was nearly two decades ago!). I feel that you need some new resources to read, research and reflect upon. Is this a project that you were forced into and are trying to adjust by chance?	[reply] [d/l]
Re^4: global var by tultalk (Monk) on Apr 05, 2017 at 21:18 UTC
I feel that you need some new resources to read, research and reflect upon. Is this a project that you were forced into and are trying to adjust by chance? Yes. From 2003	[reply]
Re^4: global var by tultalk (Monk) on Apr 05, 2017 at 21:43 UTC
Hi: Don't we all cut and paste from the internet or our own old code or code on CD's that come with textbooks? Yes we do. `use manageusers qw(LoggedOn_user_id);` [download] Software error: "LoggedOn_user_id" is not exported by the manageusers module Can't continue after import errors at update_tables-development.cgi line 30 BEGIN failed--compilation aborted at update_tables-development.cgi line 30. BEGIN { use vars qw($VERSION @ISA @EXPORT); use DBI; # $ENV{DBI_TRACE}=1; # $ENV{PERL_DBI_DEBUG}=1; require Exporter; @ISA = qw(Exporter); # exported functions our @EXPORT_OK = qw( &OpenConnection &OpenSession &ProcessLoginRequest &ProcessLostDataRequest &LoginUser &decodeEncryptedPassName &UpdateUserData &GetUserLostData &LogoutUser &GetUserSessionCookie &CheckForAuthorizedUser &Expires $attempts $adminaccess $LoggedOn_user_id <<<<<<---------------------- &Now &CheckValidLoginChar &CheckValidEmailChar &print_md5_javascript); $VERSION = '0.0.1'; } [download]	[reply] [d/l] [select]
Re^5: global var by shmem (Chancellor) on Apr 05, 2017 at 22:22 UTC
Re^6: global var by tultalk (Monk) on Apr 06, 2017 at 12:32 UTC
Some notes below your chosen depth have not been shown here
Re^5: global var by stevieb (Canon) on Apr 05, 2017 at 22:01 UTC
Re^6: global var by tultalk (Monk) on Apr 05, 2017 at 23:59 UTC
Some notes below your chosen depth have not been shown here
Re^6: global var by Anonymous Monk on Apr 05, 2017 at 23:20 UTC
Re^3: global var by GotToBTru (Prior) on Apr 05, 2017 at 20:55 UTC
Short, Self-Contained, Correct Example But God demonstrates His own love toward us, in that while we were yet sinners, Christ died for us. Romans 5:8 (NASB)	[reply]
Re^3: global var by Marshall (Canon) on Apr 06, 2017 at 13:27 UTC
To clarify (I hope) a few things about "use xxx;" `use xxx; #imports all of the symbols in @EXPORT use xxx (); #imports none of the symbols in @EXPORT #this empty list is the same as: (updated) #BEGIN { require Module } use xxx qw(OpenConnection $LoggedOn_user_id); # imports # all of the symbols in @EXPORT AND subroutine OpenConnection # AND the scalar $LoggedOn_user_id from @EXPORT_OK` [download] Update: Another attempt at explaining "use". Case 1: A plain `use xxx;` #imports all of the symbols in @EXPORT. Case2: `use xxx qw(OpenConnection $LoggedOn_user_id);` #imports only the function OpenConnection and the scalar $LoggedOn_user_id. Once a list (the parens) after the "use" shows up, this has the effect of making @EXPORT the same as @EXPORT_OK. In other words, the symbols in @EXPORT are not imported by default and must be explicitly imported like the symbols in @EXPORT_OK. Any combination of symbols in @EXPORT or @EXPORT_OK can go in this list after the "use". Case 3: (consequence of case 2), `use xxx ();` There is an empty list of stuff to import and nothing is imported - the automatic importing of the @EXPORT list is "Overridden". When you import a symbol, you can use the "short" name, e.g. `print $LoggedOn_user_id;`. If we "used" the manageusers module, but did not import $LoggedOn_user_id, that variable can still be accessed with the fully qualified name, `print $manageusers::LoggedOn_user_id;` So if you use the fully qualified name, the variable or sub name does not need to be exported (provided that you have used the module to get it loaded). Only "our" variables can be exported or accessed from another module. A "my" lexical variable cannot be. "our" puts the symbol into the package's symbol table - that means among other things that the fully qualified name is going to work. Such an operation makes no sense for a lexical scope "my" variable. File: manageusers.pm `#!/usr/bin/perl use warnings; use strict; package manageusers; BEGIN { use vars qw($VERSION @ISA @EXPORT); use DBI; # $ENV{DBI_TRACE}=1; # $ENV{PERL_DBI_DEBUG}=1; require Exporter; @ISA = qw(Exporter); # exported functions our @EXPORT_OK = qw( $attempts $adminaccess $LoggedOn_user_id Now CheckValidLoginChar CheckValidEmailChar print_md5_javascript); $VERSION = '0.0.1'; } our $LoggedOn_user_id=33; our $attempts = 99; 1;` [download] File: testManageUsers.pl `#!/usr/bin/perl use strict; use warnings; use manageusers qw($LoggedOn_user_id); print "$LoggedOn_user_id\n"; #prints 33 print "$manageusers::attempts \n"; #prints 99 #Note that $attempts is NOT <strike>exported</strike> imported, but still #can be accessed by the fully qualified name!` [download] I hope this helps. Its really early in the morning here, but I think I did this right. Run my code and then pare further questions down to just the basics and variables involved. Corrected "use xx ();" comment. A bit twitchy with the CTL-V this morning. Also changed commend about $attempts in the mail program. Thanks shmem.	[reply] [d/l] [select]
Re^4: global var by haukex (Archbishop) on Apr 06, 2017 at 14:08 UTC
`use xxx (); #imports all of the symbols in @EXPORT use xxx qw(OpenConnection $LoggedOn_user_id); # imports # all of the symbols in @EXPORT AND subroutine OpenConnection # AND the scalar $LoggedOn_user_id from @EXPORT_OK` [download] Sorry, but those two are incorrect. As per use, `use Foo ();` is exactly equivalent to `BEGIN { require Foo }`, so nothing is exported at all. When you say `use Foo qw/bar/;`, Exporter exports only that, regardless of what's in `@EXPORT`. Update: Hm, my posting seems to have overlapped with an update to the node.	[reply] [d/l] [select]
Re^5: global var by tultalk (Monk) on Apr 06, 2017 at 21:11 UTC
Re^6: global var by shmem (Chancellor) on Apr 06, 2017 at 22:14 UTC
Re^6: global var by pryrt (Abbot) on Apr 06, 2017 at 22:15 UTC
Re^4: global var by tultalk (Monk) on Apr 06, 2017 at 14:31 UTC
Hi: Thank you for this informative reply. I had not read anywhere this explanation: `use xxx; #imports all of the symbols in @EXPORT use xxx (); #imports all of the symbols in @EXPORT use xxx qw(OpenConnection $LoggedOn_user_id); # imports # all of the symbols in @EXPORT AND subroutine OpenConnection # AND the scalar $LoggedOn_user_id from @EXPORT_OK [download]` [download] I was originally used the first example and calling all the subs with manageusers::sub and I guess that is why they worked and the scalars were imported also. I recently took a fellows advice and changed the export to our EXPORT_OK and am now having to put the called subs by name in use xxx qw(sub1 sub2... sub10) to get those calls working again. I guess its back to the drawing board on this. I did read that it is not good to use xxx; as it imports everything into that module, even subs/scalars that are only for other modules. Anyway thanks for the information and with that clarification I can probably resolve my issues. Best regards	[reply] [d/l]
Re^5: global var by poj (Abbot) on Apr 06, 2017 at 15:19 UTC
Re^5: global var by Marshall (Canon) on Apr 06, 2017 at 14:54 UTC
Re^4: global var by tultalk (Monk) on Apr 06, 2017 at 17:22 UTC
Checked out the code you suggested and runs exactly as expected. Looked at my code, made sure exactly the same for the export and use and it failed exactly as before. Something is blocking the importing of the data through not exporting the $LoggedOn_user_id. I set the LoggedOn+user_id to a number to test ant did not import.	[reply]
Re^5: global var by Marshall (Canon) on Apr 08, 2017 at 03:14 UTC
Re^6: global var by tultalk (Monk) on Apr 08, 2017 at 12:21 UTC
Some notes below your chosen depth have not been shown here
Re^5: global var by poj (Abbot) on Apr 06, 2017 at 18:01 UTC
Re^6: global var by tultalk (Monk) on Apr 06, 2017 at 21:46 UTC
Some notes below your chosen depth have not been shown here
Re^6: global var by tultalk (Monk) on Apr 06, 2017 at 23:31 UTC
Some notes below your chosen depth have not been shown here


Keep It Simple, Stupid
	PerlMonks

Re: global var

Software error: