I'd first recommend taking a look at the other config modules on CPAN
and see if there's one that you can merge some of this functionality
with. See http://search.cpan.org/search?query=config&mode=dist -- there
are plenty of existing configuration modules, and you may benefit from
building on top of a module that has a wider, existing user/support
base.
That's right. I didn't know there are so many modules for reading configuration files now. Back when I needed one there were less than five modules I think, and most parsed only .ini files. That's why I wrote Data::Config in the first place.
Take Config::General for example
(http://search.cpan.org/author/TLINDEN/Config-General-2.15/General.pm).
It's similar to what you describe -- "simple assignments with
multi-lines value and nested lists, and has very few restrictions on the
data". I could see you tacking on the HTML::Template functionality as
Config::General::HTMLTemplate, or something like that. Just a
thought...
After reading the description of several modules, it appears that Config::Simple and Data::Config have a very similar API. Plus Config::Simple supports more than one format, whereas Config::General seems to only read Apache-style format.
After some quick tests, it seems that Config::Simple has its own internal structure, which is not compatible with Data::Config (in fact, with HTML::Template as I use the same structure).
If you still decide to branch out on your own, I'd recommend sticking with the Config:: namespace, given that that's where all/most of the modules with similar functionality are.
From my tests, I don't think I'll be able to reprogram Data::Config as a subclass or a subpart of another existing module, so I will release it on its own, probably under the name Config::Natural unless somebody has a better idea.
Anyway, thanks for your help.
S�bastien Aperghis-Tramoni -- - --- -- - -- - --- -- - --- -- - --[ http://maddingue.org ]
