in reply to Toolset configuration
Or...
The object-oriented model fits this scenario. Your config package would load the config files into what will later be private (local) scope (during the change process you have to let old code break that rule) and later hand it out to tools via new methods that have parameters as necessary to fully specify the configuration value being requested.
You set about modifying your tools to use the new methods instead of accessing the data structure directly. Only when that process is complete have you made your tools independent of data structure.
One world, one people
|
|---|
In Section
Seekers of Perl Wisdom