The Exporter module implements an "import" method which allows a module to export functions and variables to its users' namespaces. Many modules use Exporter rather than implementing their own "import" method because Exporter provides a highly flexib...

This main incentive in creating this exporter is to allow modules to be updated and get rid of default exports in newer releases, while still maintaining compatibility with older code. What it Gives the Client's 'use' Statement If ModuleName gets its...

Implements the standard conventions for import of PDL modules in to the namespace Hopefully will be extended to allow fine control of which namespace is used....

ACHTUNG! If you're not familiar with Exporter or exporting, read Sub::Exporter::Tutorial first! Why Generators? The biggest benefit of Sub::Exporter over existing exporters (including the ubiquitous Exporter.pm) is its ability to build new coderefs f...

This module implements a SIOC exporter class. It will output the RDF representation of SIOC objects passed to it....

Exporter::Lite is an alternative to Exporter, intended to provide a lightweight subset of the most commonly-used functionality. It supports "import()", @EXPORT and @EXPORT_OK and not a whole lot else. Unlike Exporter, it is not necessary to inherit f...

Exporter::Tiny supports many of Sub::Exporter's external-facing features including renaming imported functions with the "-as", "-prefix" and "-suffix" options; explicit destinations with the "into" option; and alternative installers with the "install...

Exporter::Easy makes using Exporter easy. In its simplest case, it allows you to drop the boilerplate code that comes with using Exporter, so require Exporter; use base qw( Exporter ); use vars qw( @EXPORT ); @EXPORT = ( 'init' ); becomes use Exporte...

Implements the standard conventions for import of PDLA modules in to the namespace Hopefully will be extended to allow fine control of which namespace is used....

Exporter::Auto is a simple replacement for Exporter that will export all public functions from your package. If you want all functions to be exported from your module by default, then this might be the module for you. If you only want some functions ...

This module serves as an easy, clean alternative to Exporter. Unlike Exporter, it is not subclassed, but it simply exports a custom import() into your namespace. With Exporter::Tidy, you don't need to use any package global in your module. Even the s...

This installs 'import' and 'exports' subroutines into the callers namespace. The 'import' does the usual deed: exporting symbols by name; 'exports' simplifies introspection by listing the exported symbols (useful for testing). The optional "dispather...

No user-serviceable parts inside....

This module encapsulates the exporting of sugar functions in a "Moose.pm"-like manner. It does this by building custom "import" and "unimport" methods for your module, based on a spec you provide. It also lets you "stack" Moose-alike modules so you c...

This module allows you to declare constants that can be exported to other modules. To declare constants, simply group then into export tags: package MyApp::Constants; use Const::Exporter tag_a => [ 'foo' => 1, 'bar' => 2, ], tag_b => [ 'baz' => 3, 'b...

This is a very small wrapper to simplify using Exporter::Tiny. It does the following: * Marks your package as loaded in %INC; * Pushes any function names in the import list onto your @EXPORT_OK; and * Pushes "Exporter::Tiny" onto your @ISA. It doesn'...

This module encapsulates the exporting of sugar functions in a "Mouse.pm"-like manner. It does this by building custom "import", "unimport" methods for your module, based on a spec you provide. Note that "Mouse::Exporter" does not provide the "with_m...

This module makes it much easier to make a module have a hybrid object/method interface similar to the one of CGI.pm. You can take any old module that has an object- oriented interface and convert it to have a hybrid interface by simply adding "use b...

Exporter::Rinci is a simple wrapper for Exporter. Before handing out control to Exporter's import(), it will look at the exporting module's @EXPORT, @EXPORT_OK, and %EXPORT_TAGS and if they are empty will fill them out with data from Rinci metadata (...

This module, when subclassed by a package, allows that package to define exports in a more concise way than using "Exporter". Instead of having to worry what goes in @EXPORT, @EXPORT_OK and %EXPORT_TAGS, you can use two attributes to define exporter ...