perl-config-pref Code
Status: Alpha
Brought to you by:
dallaylaen
File | Date | Author | Commit |
---|---|---|---|
lib | 2011-08-06 |
![]() |
[79f338] VERSION 0.09003 released. Fix bug #1 |
t | 2011-08-06 |
![]() |
[322daa] Fixed backshash/newline behaviour. |
.gitignore | 2011-07-30 |
![]() |
[557dff] Support files cleanup |
Changes | 2011-08-06 |
![]() |
[79f338] VERSION 0.09003 released. Fix bug #1 |
MANIFEST.SKIP | 2011-07-30 |
![]() |
[bf1f51] Updated MANIFEST.SKIP |
Makefile.PL | 2011-07-30 |
![]() |
[557dff] Support files cleanup |
README | 2011-03-31 |
![]() |
[a0106f] VERSION 0.12; SAVE works; fixed README |
TODO | 2011-08-06 |
![]() |
[322daa] Fixed backshash/newline behaviour. |
version_update | 2011-07-31 |
![]() |
[fd2783] VERSION 0.09001 released |
Config-Pref This is yet another config file format module. Its ultimate goal is to access reasonably complex configuration format using as few keystrokes as possible. It was heavily influenced by Config::Gitlike and YAML. What it can: * load, save, and validate itself. * unnested lists [] and hashes {} are supported. * config can %include another config. * unnamed [sections] serve as default values for [named "ones"]. Why not XML? Because this sample amounts to four levels of indentation in XML, yet remains completely human-editable: [foo "bar"] baz = {one:1, two:2} That said, XML support as an alternate IO format is planned. WHY NOT YAML? Because I like good old .ini files. YAML support as an IO format is planned. INSTALLATION To install this module, run the following commands: perl Makefile.PL make make test make install SUPPORT AND DOCUMENTATION perldoc Config::Pref COPYRIGHT AND LICENCE Copyright (C) 2010 Konstantin S. Uvarin This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.