A simple test of his assumption should be enough to convince:

foo.pm: 

  package foo;
  BEGIN { print "foo's BEGIN\n"; }
  print "foo's body\n";
  sub import {
    shift @_;
    print "foo's import: @_\n";
  }
  1;

[download]

bar.pm: 

  package bar;
  use foo qw(from bar);
  1;

[download]

test.pl: 

  use lib '.';
  use foo qw(from test.pl);
  use foo qw(from test.pl again);
  use bar;

[download]

Output: 

  $ perl test.pl
  foo's BEGIN
  foo's body
  foo's import: from test.pl
  foo's import: from test.pl again
  foo's import: from bar
  $

[download]
BEGIN blocks are executed at compilation. use and require don't compile the same code twice.

Look in perlvar under %INC for more info:

The "require" operator uses this hash to determine whether a particular file has already been included.

blokhead

In reply to Re: use and BEGIN by blokhead
in thread use and BEGIN by tall_man

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.