in reply to Re: Should you use a module to hold configuration items?
in thread Should you use a module to hold configuration items?

You could, cautiously, say that such a design is “elegant,” if the design that you are stuck with is that “there are a bunch of separate scripts.”   (Whether or not you think that having “there are a bunch of separate scripts” qualifies as “elegant” is beside the point.)   All of the configuration options become available with one simple use statement.   No separate parsing is required:   the .pm file is the configuration file.   If the options, once set, almost never ever change, that works.

  • Comment on Re^2: Should you use a module to hold configuration items?