1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
|
Source: libload-perl
Maintainer: Debian Perl Group <pkg-perl-maintainers@lists.alioth.debian.org>
Uploaders: gregor herrmann <gregoa@debian.org>
Section: perl
Testsuite: autopkgtest-pkg-perl
Priority: optional
Build-Depends: debhelper-compat (= 12)
Build-Depends-Indep: perl
Standards-Version: 4.4.1
Vcs-Browser: https://salsa.debian.org/perl-team/modules/packages/libload-perl
Vcs-Git: https://salsa.debian.org/perl-team/modules/packages/libload-perl.git
Homepage: https://metacpan.org/release/load
Package: libload-perl
Architecture: all
Depends: ${misc:Depends},
${perl:Depends}
Description: pragma for controlling when subroutines will be loaded
The "load" pragma allows a module developer to give the application developer
more options with regards to optimize for memory or CPU usage. The "load"
pragma gives more control on the moment when subroutines are loaded and start
taking up memory. This allows the application developer to optimize for CPU
usage (by loading all of a module at compile time and thus reducing the
amount of CPU used during the execution of an application). Or allow the
application developer to optimize for memory usage, by loading subroutines
only when they are actually needed, thereby however increasing the amount of
CPU needed during execution.
.
The "load" pragma combines the best of both worlds from AutoLoader and
SelfLoader. And adds some more features.
.
In a situation where you want to use as little memory as possible, the "load"
pragma (in the context of a module) is a drop-in replacement for AutoLoader.
But for situations where you want to have a module load everything it could
ever possibly need (e.g. when starting a mod_perl server in pre-fork mode),
the "load" pragma can be used (in the context of an application) to have all
subroutines of a module loaded without having to make any change to the
source of the module in question.
|
