in reply to Modules: computing a constant, "on load" or in new()?
Putting them in new means doing the same work over. That's a waste of cpu and a violation of DRY principle.
There is nothing 'dirty' about setting up the 'constant' requirements of your module at load time.
Indeed, that exactly what you are doing when you declare your functions.
sub XYZ { ...} is exactly the same as *{__PACKAGE__'::XYZ'} = sub { ... };; it is a load-time assignment to a symbol in your package stash.
With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
|
|---|
In Section
Seekers of Perl Wisdom