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.

In reply to Re^2: global var by tultalk
in thread global var by tultalk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.