There are plenty of legitimate reasons to want to have
more complex data structures in a configuration than
just a simple hash.
Also while there are plenty of configuration modules on
CPAN, I haven't seen any that I like very much. Here are
the main capabilities that I want out of a configuration
- Be able to have any kind of data structure into
- Be able to have a search path with selective
overriding of configuration information. For instance
the development and production configurations should be
as similar as possible, with only a few key values being
- Be able to selectively tie together the
configurations of separate modules which should share some
common information based on your environment.
- Have checks so that if someone is trying to access
a variable from the configuration that isn't there, you
can catch it and fix.
On these criteria, most of the CPAN configuration modules
score 0/4. Just using raw Perl as a configuration file
scores 2/4. A simple bit of code that searches a
configuration path and do
es every file it finds there
with a specific name scores 3/4. And if you know what
you are doing, it is possible to create a simple
configuration module that adds the export checks.
Now those wants are not everyone's. Everyone wants to
get different things from a configuration module (which is
one reason why there are so many configuration modules out
there). But I claim that my list is not an unreasonable
set of wants for a Perl programmer to have, and if you
have them then pure Perl is a perfectly reasonable kind of
configuration file to use.
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link or
or How to display code and escape characters
are good places to start.