Lines Matching refs:module
104 In module YourModule.pm:
124 The Exporter module implements an C<import> method which allows a module
131 C<use> statement for a module. Modules and C<use> are documented
138 The arrays C<@EXPORT> and C<@EXPORT_OK> in a module hold lists of
157 Exports pollute the namespace of the module user. If you must export
162 module using the ModuleName::item_name (or $blessed_ref-E<gt>method)
175 As a general rule, if the module is trying to be object oriented
181 Other module design guidelines can be found in L<perlmod>.
185 In other files which wish to use your module there are three basic ways for
186 them to load your module and import its symbols:
197 This causes perl to load your module but does not import any symbols.
269 For example, suppose that you have a module, A, which already has an
282 and you want to Export symbol $A::b back to the module that called
298 the program or module that used package A.
318 The Exporter module will convert an attempt to import a number from a
319 module into a call to $module_name-E<gt>require_version($value). This can
320 be used to validate that the version of the module being used is
323 The Exporter module supplies a default require_version method which
324 checks the value of $VERSION in the exporting module.
340 If a module attempts to import any of these symbols the Exporter
341 will give the module an opportunity to handle the situation before