If your config data is only read by perl, write the config data in plain perl, and load the files via require. If you need your data to be portable between applications, use XML.
Writing plain perl has the disadvantage of curlies, brackets, parens and commas - and the big advantage of being perl. If you need a config file format with less line noise and (probably) understandable for non-perl people, have a look at Config::Simple.
--shmem
_($_=" "x(1<<5)."?\n".q·/)Oo. G°\ /
/\_¯/(q /
---------------------------- \__(m.====·.(_("always off the crowd"))."·
");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}
| [reply] |
Plain Perl is out since I do need to allow non-perl people set their own configurations. I will take a look at Config::Simple but am getting a little Syck and am liking it.
ab_iron
| [reply] |
YAML::ConfigFile seems to come with the standard distribution.
Curiously, it doesn't seem to be on cpan... But it may suit your purposes.
| [reply] |
| [reply] |