Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl: the Markov chain saw

Re: Writing Modules/namespace polution

by ikegami (Pope)
on Mar 16, 2005 at 15:58 UTC ( #439992=note: print w/replies, xml ) Need Help??

in reply to Writing Modules/namespace polution

Your name space isn't poluted:

use strict; use warnings; use mymodule; print "My Test\n"; Func1(); # ERROR! Func2("Fluffy", 5); # ERROR!

But check this out:

use strict; use warnings; use mymodule qw( Func1 ); # Import Func1 #use mymodule qw( Func2 ); # This won't work since # Func2 is not in @EXPORT_OK. print "My Test\n"; Func1(); Func2("Fluffy", 5); # ERROR!

You should never export methods. As you can see, there's no reason to do so. All functions in a package are tied to the object blessed to that package, whether you use Exporter or not.

and how can I prevent it as it seems to be allowing everything into the calling script's namespace?

It's possible to disguise a function using lexicals and/or closures so that noone outside the package can call it, but there's no need to do so. Write proper documentation instead.

Replies are listed 'Best First'.
Re^2: Writing Modules/namespace polution
by thekestrel (Friar) on Mar 16, 2005 at 16:18 UTC
    Thanks ikegami,
    I can see how the exporter is supposed to work now. I read so much on making modules and looking at what other people had done, I just ended up combining both ideas which was wrong.
    Regards Paul.

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://439992]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others exploiting the Monastery: (5)
As of 2020-10-29 17:37 GMT
Find Nodes?
    Voting Booth?
    My favourite web site is:

    Results (274 votes). Check out past polls.