Bug#483894: RFP: libconfig-scoped-perl -- feature rich configuration file parser
Package: wnpp
Severity: wishlist
* Package name : libconfig-scoped-perl
Version : 0.12
Upstream Author : Karl Gaissmaier <karl.gaissmaier at uni-ulm.de>
* URL : http://search.cpan.org/~gaissmai/Config-Scoped-0.12/lib/Config/Scoped.pm
* License : This library is free software; you can
redistribute it and/or modify it under the same
terms as Perl itself.
Programming Lang: Perl
Description : feature rich configuration file parser
Config::Scoped is a configuration file parser for complex
configuration files based on Parse::RecDescent. Files similar to the
ISC named or ISC dhcpd configurations are possible. In order to be
fast a precompiled grammar and optionally a config cache is used.
Config::Scoped has the following highlights as a configuration file parser:
* Complex recursive datastructures to any extent with scalars,
lists and hashes as elements,
* As a subset parses any complex Perl datastructures (no
references and globs) without do or require,
* Include files with recursion checks,
* Controlled macro expansion in double quoted tokens,
* Lexically scoped parameter assignments and pragma directives,
* Perl quote like constructs to any extent, '', "", and here docs <<,
* Perl code evaluation in Safe compartments,
* Caching and restore with MD5 checks to determine alterations in
the original config files,
* Standard macro, parameter, declaration redefinition validation,
may be overridden to validate on semantic knowledge,
* Standard file permission and ownership safety validation, may be
overridden,
* Fine control for redefiniton warnings with pragma's and other
safety checks,
* Easy inheritable, may be subclassed to build parsers with
specialized validation features,
* Condoning syntax checker, semicolons and or commas are not
always necessary to finish a statement or a list item if the end
can be guessed by other means like newlines, closing brackets,
braces etc.,
* Well spotted messages for syntax errors even within include
files with correct line numbers and file names,
* Exception based error handling,
Reply to: