Beefy Boxes and Bandwidth Generously Provided by pair Networks
No such thing as a small change

Module usage

by vinoth.ree (Monsignor)
on Feb 26, 2009 at 03:36 UTC ( #746438=perlquestion: print w/replies, xml ) Need Help??
vinoth.ree has asked for the wisdom of the Perl Monks concerning the following question:

use Mymodule ();

If I am including a package into my program means I may use variables or functions from that package, but I read that the above line will import nothing, So what is the use of the above line in my perl program ?

Replies are listed 'Best First'.
Re: Module usage
by GrandFather (Sage) on Feb 26, 2009 at 06:53 UTC

    Many modules by default export a bunch of functions into the current package (whatever has the use Mymodule; in it). By including an empty list in the use you explicitly forbid anything from Mymodule being exported into the package name space. That doesn't stop you accessing the module's functions however. You just prefix the function name with the module name: Mymodule::wibble () for example to call the wibble function from the Mymodule module.

    Why bother? Well, modules tend to be designed in isolation so very often functions that perform similar tasks get the same name in different modules. If all the functions were imported from every module that is used in a package then the chance of collisions between function names becomes very high - using name spaces as above completely avoids the problem.

    Another advantage of using explicit name spaces is that then it is clear where the function comes from. I always use CGI with an empty list for example and then either use the OO interface CGI provides or call functions using an explicit CGI:: prefix.

    True laziness is hard work
Re: Module usage
by jasonk (Parson) on Feb 26, 2009 at 03:39 UTC

    If MyModule has exports you don't want, passing an empty list as an argument will keep them from being imported. You still need to load the module, however, if you want to do something like MyModule->new.
    We're not surrounded, we're in a target-rich environment!
Re: Module usage
by ww (Archbishop) on Feb 26, 2009 at 04:07 UTC

    That module MAY export some functions, etc. by default, which action you can override with the empty parentheses. (You may find jasonk's statement clearer) But note, you will have access to those when your code includes use MyModule; and subsequently specifies some particular exportable therefrom.

    So, if you wish to make use of some exportable function from a module when (and only when) a particular condition in your code is reached (think "dispatch table", for example) but another exportable function if a different condition is reached, you might find the empty parentheses useage handy (when followed by the likes of MyModule -> new in a dispatch table (or elsewhere).

    Some other references you may find helpful:
    • perldoc perlmod
    • The Tutorials here, under the heading "Modules: How to Create, Install, and Use"
    • Printed discussions such as those in "Intermediate Perl"
Re: Module usage
by Your Mother (Chancellor) on Feb 26, 2009 at 05:27 UTC

    Sometimes it's also valuable to be able to have CGI::Dump and YAML::Dump and XYZ::Dump all within reach but not stomping on each other through an exportarama. Also it makes us feel more sympathy for our disadvantaged brethren when we're able to type-

    my $it = Org::PerlMonks::WWW::Everything::View::Page::Nodelet::DailyBe +st::GetIterator();
Re: Module usage
by cdarke (Prior) on Feb 26, 2009 at 09:04 UTC
    Also remember that useing a module might well execute code. There are a number of code blocks which are executed at parse/compile time, the most common being BEGIN{...} blocks. Any code in the module not within a function will also be executed at this time. Code can also be executed on process closedown inside an END{...} block.

    So a module might be doing some magic without you realising it, and you do not need to explicitly call a single function to do that, use is enough.
Re: Module usage
by ig (Vicar) on Feb 26, 2009 at 09:53 UTC

    This is essentially the same answer as others have provided but if you don't understand their answers perhaps this manner of expressing them will help...

    'use Mymodule ();' causes Mymodule to be loaded without calling its import() subroutine. This makes the subroutines of the module available and will cause BEGIN, UNITCHECK, CHECK and INIT blocks to be executed if they exist.

    The import() subroutine of many (not all) modules will add variables or subroutines to the callers name space.

    You sometimes want to load the module but do not want it to add anything to your name space. For example - you may have your own subroutines of the same name as the module would create (import) if its import() subroutine was called.

    Having loaded the module, you can access its subroutines using fully qualified subroutine or method calls. For example, Mymodule::some_subroutine() or Mymodule->some_method.

    In some modules the import() subroutine does other things as well as or instead of importing names into the callers name space. If the module is doing initialization in its import() subroutine, then it may not work as expected when you prevent the subroutine being called. You should read the documentation or the code of the module you are using to be sure.

Re: Module usage
by eye (Chaplain) on Feb 26, 2009 at 09:59 UTC
    Including a module with "use" reads the module and makes it available to your program within its own namespace. By default, many modules will export symbols (variables, functions, methods, etc.) into the "main::" namespace. This allows you access to these symbols without prefixing them with their proper namespace. Specifying a list of symbols with the "use" statement overrides the choice of symbols to export. When this list is empty, no symbols are exported. The symbols are still accessible by prefixing them with the namespace of the module.
      By default, many modules will export symbols ... into the "main::" namespace.

      That is incorrect, but it is often what happens because the use Module statement is in the package main. The symbols are exported to into the current namespace.

      Be well,

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: perlquestion [id://746438]
Approved by ww
and a log crumbles through the grate...

How do I use this? | Other CB clients
Other Users?
Others wandering the Monastery: (5)
As of 2017-06-28 04:22 GMT
Find Nodes?
    Voting Booth?
    How many monitors do you use while coding?

    Results (623 votes). Check out past polls.