in reply to RFC: Config::File

  1. Using Perl code as the config format is usualy not that a good idea. Especialy if there will be other people editing the config file(s). It's too easy to break something (or into something).
  2. I don't think croaking on keys not present in the config file is such a great idea. Undef always works better for me.
  3. I don't understand why would anyone want to separate the filename and path and have your module put them together.
  4. There are too many config related modules on CPAN already.

You'd better use YAML or XML. IMHO of course.

Jenda
Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live.
   -- Rick Osborne

Edit by castaway: Closed small tag in signature

Replies are listed 'Best First'.
Re: Re: RFC: Config::File
by Rich36 (Chaplain) on Feb 10, 2004 at 22:27 UTC

    "You'd better use YAML or XML. IMHO of course."

    For simple config files, I've found that XML::Simple is a good solution.

    «Rich36»
[reply]

In Section Meditations