in reply to Another config file module (any alternative to symbolic refs?)

The answer to the first question is that this is why Perl allows symbolic references. There are other alternatives, but they work out to be worse in this case.

The answer to the second question is that your module should have a function called import. That will be called as a method when you use the module, and you can use that to let the calling module explain what it wants to ask for, elminating your synchronization problem.

The random tidbit that I think will be most likely to help is that you should have a search path that is readily configurable, and if at all possible you should set things up so that you can selectively override information in the path, and so that in development you pick up information differently from what you do in production.

This will make testing, developing, and deploying your system much simpler and more flexible.

  • Comment on Re (tilly) 1: Another config file module (any alternative to symbolic refs?)