Adekunle Olonoh <[EMAIL PROTECTED]> writes:
> I don't mean to be negative, but there are a *LOT* of config-related
> modules on CPAN right now and IMHO, the differences you've shown don't
> seem to warrant another yet another config module.
With that reasoning, you can purge 80% of CPAN.
> Have you contacted
> the author of Config::Properties to see if he'd be interested in merging
> your changes into it? That may be a good first step to take.
That may be a future step, once the functionality stabilizes.
> There are a lot of alpha modules on CPAN, but instead of adding another
> alpha module I'd encourage you to work towards bringing an existing one
> to beta or release status.
I mentioned three reasons for not choosing YAML, of wich the alpha
status is least important. I know the quality of Ingy's work.
> Have you looked at Config::General? It looks mature, full-featured,
> simple to use, and basically meets all your requirements.
I'll summarize the requirements (design goals):
- properties must be hierarchical of unlimited depth;
- manual editing of the property files (hence unambiguous syntax and
lay out);
- it must be possible to locate all subkeys of a property in the
order they appear in the property file(s);
- lightweight so shell scripts can use it to query properties.
Besides, the module _is_ already there. It just needs a name and
upload ;-)
-- Johan
