The ConfigReader library is a set of classes which reads
directives from a configuration file. The library is
completely object oriented, and it is envisioned that
parsers for new styles of configuration files can be
easily added.
ConfigReader::Spec encapsulates a specification for
configuration directives. You can specify which
directives can be in the configuration file, aliases for
the directive, whether the directive is required or has a
default value, and how to parse the directive value.
Here's an example of how one directive might be specified:
required $spec 'HomePage', 'new URI::URL';
This defines a required directive called 'HomePage'. To
parse the value from the configuration file, the
URI::URL::new() method will be called with the string
value as its argument.
use 'perldoc ConfigReader' for more information.
Config::Merge - load a configuration directory tree
containing YAML, JSON, XML, Perl, INI
or Config::General files
Config::Model::Tester provides a way to test configuration models with tests
files. This class was designed to tests several models and several tests cases
per model.
dbus-c++ attempts to provide a C++ API for D-BUS. The library has a
glib/gtk and an Ecore mainloop integration. It also offers an optional
own main loop.
This module extends Config::INI to support reading and writing
MySQL-style configuration files. Although deceptively similar to
standard .INI files, they can include bare boolean options with no
value assignment and additional features like !include and
!includedir.
The Config::Objective module provides a mechanism for parsing config files
to manipulate configuration data. Unlike most other config file modules,
which represent config data as simple variables, Config::Objective
represents config data as perl objects. This allows for a much more
flexible configuration language, since new classes can be easily written
to add methods to the config syntax.
Structured data retreival of perl -V output
This module provides an API for loading and saving of simple configuration
file records. Entries in the configuration file are essentially key,value
pairs, with the key and values separated by a single equals symbol. The
key consists only of alphanumeric characters. There are three types of
values, scalar values can contain anything except newlines. Trailing
whitespace will be trimmed unless the value is surrounded in double
quotes.
A perl module that is designed to provide easy to use settings
files for your project. You subclass the basic Config::Setting
class in one of your own modules, and then provide an interface to
your code using it. When set up, you can then override the settings
on a per-host basis, or even using an environment variable.
By default a win.ini style of configuration is used, but this can
be overridden and an XML based configuration is also included. The
access mechanism can also be overridden, the setting don't have to
come from a file, but (maybe) from a web site. You'll have to write
your own there, though.
This module implements yet another damn configuration-file system.
The configuration language is deliberately simple and limited, and the
module works hard to preserve as much information (section order,
comments, etc.) as possible when a configuration file is updated.
See Chapter 19 of "Perl Best Practices" (O'Reilly, 2005) for the
rationale for this approach.
The configuration language is a slight extension of the Windows INI
format.