Shmuel, 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.
Thanks, David On Sun, Mar 20, 2011 at 11:02 AM, Shmuel Fomberg <[email protected]> wrote: > Hi David. > > what good will it do, if the class is defined in other file? > > Shmuel. > > 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. >> >> David >> >> On Sun, Mar 20, 2011 at 8:48 AM, Gabor Szabo<[email protected]> 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. >>> >>> Gabor >>> >> _______________________________________________ >> Perl mailing list >> [email protected] >> http://mail.perl.org.il/mailman/listinfo/perl >> > > _______________________________________________ > Perl mailing list > [email protected] > http://mail.perl.org.il/mailman/listinfo/perl > _______________________________________________ Perl mailing list [email protected] http://mail.perl.org.il/mailman/listinfo/perl
