you already had the perfect, concise answer by choroba, but let me expand something that can be useful.

 use Module;   <=>  BEGIN { require Module; Module->import( LIST ); }

ikegami on SO explains it in this way:

# script.pl
use Foo;
my $foo = Foo->new();
$foo->do();

# does:

1.Compile script.pl
  1.Compile use Foo;
  2.Execute require Foo;
    1.Compile Foo.pm
      1. ...
    2.Execute Foo.pm
      1. ...
  3.Execute import Foo;
  4.Compile my $foo = Foo->new();
  5.Compile $foo->do();
2.Execute script.pl
  1.Execute my $foo = Foo->new();
  2.Execute $foo->do();
[download]

Wich unveils the compiletime/runtime dicotomy.

Also very interesting read is Re: RunTime & compile Time Doubt on Perl (many) and the document I always called twelve pillars of wisdom (but i do not remember if it was named this way..) as found in perlmod

  print         "10. Ordinary code runs at runtime.\n";
  END { print   "16.   So this is the end of the tale.\n" }
  INIT { print  " 7. INIT blocks run FIFO just before runtime.\n" }
  UNITCHECK { print       " 4.   And therefore before any CHECK blocks
+.\n"  }
  CHECK { print " 6.   So this is the sixth line.\n" }
  print         "11.   It runs in order, of course.\n";
  BEGIN { print " 1. BEGIN blocks run FIFO during compilation.\n" }
  END { print   "15.   Read perlmod for the rest of the story.\n" }
  CHECK { print " 5. CHECK blocks run LIFO after all compilation.\n" }
  INIT { print  " 8.   Run this again, using Perl's -c switch.\n" }
  print         "12.   This is anti-obfuscated code.\n";
  END { print   "14. END blocks run LIFO at quitting time.\n" }
  BEGIN { print " 2.   So this line comes out second.\n" }
  UNITCHECK { print " 3. UNITCHECK blocks run LIFO after each file is 
+compiled.\n"  }
  INIT { print  " 9.   You'll see the difference right away.\n" }
  print         "13.   It only _looks_ like it should be confusing.\n"
+;
[download]

other interesting reads are at your disposal in my bibliotheca

L*