Renaming of Config::Loader

CPAN::Forum

Config-Loader - Renaming of Config::Loader

Config-Loader [search.cpan.org] [Kobes search] [View and report bugs] [Ratings 0.0

(0) ]

[AnnoCPAN] [CPAN Tests results] [CPANTS]

Posted on Thu Aug 23 10:54:09 2007 by clinton

Renaming of Config::Loader

Config::Loader takes a directory tree of configuration files (in XML, YAML, JSON, INI etc) and merges them into a single hash. It's merge policy allows for the overriding of individual keys locally, to allow easy separation of production and development environments. This merge policy can be customised with regexes or callbacks.

I'm currently trying to register the namespace, and the feedback has been that Config::Loader is not descriptive enough of what the module actually does.

brian.d.foy has suggested Config::Any::Merge. My opinion is below. Do you have any suggestions?

thanks

Clint

Pros for "Config::Any::Merge": - the Any implies the multiple formats - the Merge describes what it does, merging trees of config files, plus local overrides - the Config::Any namespace has traction, which might lead people on to my module Cons for "Config::Any::Merge": - it implies an interface relationship with Config::Any which there isn't - it hides the module away under a 3rd level namespace which also makes (eg) Config::Any::Merge::Writer quite a keyboardfull :) Other suggestions: - Config::Merge (the author has offered to vacate the namespace) - Config::Tree (does the Tree imply something else?)

Write a response

Service launched on 2nd of February 2005.
Comments, and other submissions on CPAN Forum are Copyright 2005-2007, their respective owners.
Site maintainer is not responsible for content. Privacy Policy

Maintained and hosted by Gabor Szabo at Perl Training Israel