Update: For those who (understandably) don't realize that there really is pertinent information for this thread available if you follow the above link (slightly paraphrased):
The documentation lays out best practices for ensuring that initialization will always be done before it is needed and not before it is possible, even when complex interdependencies between initialization steps exist.
Devel::Init allows module authors to declare what initialization steps are required and then allows each situation to very easily drive which types of initializations should be run when (and which types should not be run until they are actually needed).
And Devel::Init makes it easy to write your initialization code so that a circular dependency will be detected and be reported in an informative way.
- tye
In reply to Re: Module for executing postponed initialization code (Devel::Init)
by tye
in thread Module for executing postponed initialization code
by Dallaylaen
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |