Lines Matching defs:export

21 sub export {
39   return export $pkg, $callpkg, @_
59   return export $pkg, $callpkg, ($args ? @_ : ()) if $heavy;
75 # Otherwise we could have aliased them to export().
106   our @EXPORT_OK = qw(munge frobnicate);  # symbols to export on request
113   our @EXPORT_OK = qw(munge frobnicate);  # symbols to export on request
119   our @EXPORT_OK = qw(munge frobnicate);  # symbols to export on request
132 to export functions and variables to its users' namespaces.  Many modules
160 Do B<not> export method names!
162 Do B<not> export anything else by default without a good reason!
164 Exports pollute the namespace of the module user.  If you must export
183 then export nothing.  If it's just a collection of functions then
186 ampersands for the export lists.
210 occurs.  The advanced export features of Exporter are accessed like this,
276 to export your symbols, and C<@what_to_export> is an array telling what
277 symbols *to* export (usually this is C<@_>).  The C<$package> argument is
308 This will export the symbols one level 'above' the current package - ie: to 
323 which will export Exporter's own import() method into YourModule.
365 export fails.  The Exporter provides a default C<export_fail> method which
493     our @EXPORT_OK = qw(munge frobnicate);  # symbols to export on request
506     our @EXPORT_OK = qw(munge frobnicate);  # symbols to export on request
546 to not export:
567 export variable names.  Just because C<Exporter> lets you