in reply to Re^2: Modules: computing a constant, "on load" or in new()?
in thread Modules: computing a constant, "on load" or in new()?
"If one were dealing with a lexical variable as in your example, and if the class was defined entirely within a file, and if the file/module was loaded only via a use statement, what would be the advantage of postponing initialization?"
There might be a few dozen such items, each of which is reasonably costly to compile, and in a particular invocation of the program, only one or two (or perhaps even none in the case where the program has been invoked with the --help parameter) actually need to be used.
package Cow { use Moo; has name => (is => 'lazy', default => sub { 'Mooington' }) } say Cow->new->name
|
---|
Replies are listed 'Best First'. | |
---|---|
Re^4: Modules: computing a constant, "on load" or in new()?
by AnomalousMonk (Archbishop) on Sep 08, 2013 at 04:17 UTC |
In Section
Seekers of Perl Wisdom