[Israel.pm] use and require
davidlbaird at gmail.com
Sun Mar 20 02:33:39 PDT 2011
On more complex systems, deferring loading the other file when the
class is needed can potentially cut down on the number of modules that
need to be compiled. I've seen complex frameworks where only 10% to
20% of the modules compiled are actually utilized by a given script.
On Sun, Mar 20, 2011 at 11:02 AM, Shmuel Fomberg <owner at semuel.co.il> wrote:
> Hi David.
> what good will it do, if the class is defined in other file?
> On 2011/03/20 16:54, David Baird wrote:
>> IMHO, a nice change to Perl would be to defer loading class modules
>> until the first Class::Module->new() statement is encountered, and at
>> that point, Perl would "require" but not "import" the module. This is
>> sufficient for most class modules, and would save time on initial
>> loading of a script.
>> On Sun, Mar 20, 2011 at 8:48 AM, Gabor Szabo<szabgab at gmail.com> wrote:
>>> I think it totally depends on the usage pattern. For a persistent web
>>> application loading everything up front won't hurt performance.
>>> For an editor where people want to start typing ASAP and don't
>>> want to wait for all the subsystems to load you will serve them better
>>> by delaying everything as much as possible.
>> Perl mailing list
>> Perl at perl.org.il
> Perl mailing list
> Perl at perl.org.il
More information about the Perl