AutoSplit - split a package for autoloading
- autosplit($file, $dir, $keep, $check, $modtime);
This function will split up your program into files that the AutoLoader module can handle. It is used by both the standard perl libraries and by the MakeMaker utility, to automatically configure libraries for autoloading.
interface splits the specified file into a hierarchy
rooted at the directory
. It creates directories as needed to reflect
class hierarchy, and creates the file autosplit.ix. This file acts as
both forward declaration of all package routines, and as timestamp for the
last update of the hierarchy.
The remaining three arguments to
govern other options to
If the third argument, $keep, is false, then any
*.al files in the autoload directory are removed if
they are no longer part of the module (obsoleted functions).
$keep defaults to 0.
fourth argument, $check, instructs
to check the module
currently being split to ensure that it includes a
specification for the AutoLoader module, and skips the module if
AutoLoader is not detected.
$check defaults to 1.
Lastly, the $modtime argument specifies
is to check the modification time of the module
against that of the
file, and only split the module if
it is newer.
$modtime defaults to 1.
Typical use of AutoSplit in the perl MakeMaker utility is via the command-line with:
- perl -e 'use AutoSplit; autosplit($ARGV, $ARGV, 0, 1, 1)'
Defined as a Make macro, it is invoked with file and directory arguments;
will split the specified file into the specified directory and
.al files, after checking first that the module does use
the AutoLoader, and ensuring that the module is not already currently split
in its current form (the modtime test).
form is used in the building of perl. It takes
as input a list of files (modules) that are assumed to reside in a directory
lib relative to the current directory. Each file is sent to the
autosplitter one at a time, to be split into the directory lib/auto.
In both usages of the autosplitter, only subroutines defined following the perl __END__ token are split out into separate files. Some routines may be placed prior to this marker to force their immediate loading and parsing.
As of version 1.01 of the AutoSplit module it is possible to have multiple packages within a single file. Both of the following cases are supported:
will inform the user if it is necessary to create the
top-level directory specified in the invocation. It is preferred that
the script or installation process that invokes
created the full directory path ahead of time. This warning may
indicate that the module is being split into an incorrect path.
will warn the user of all subroutines whose name causes
potential file naming conflicts on machines with drastically limited
(8 characters or less) file name length. Since the subroutine name is
used as the file name, these warnings can aid in portability to such
Warnings are issued and the file skipped if
either the __END__ marker or a "package Name;"-style specification.
will also emit general diagnostics for inability to
create directories or files.