Subject: | Subclassing in the Config::Any Namespace |
Date: | Tue, 11 Nov 2008 12:59:02 +0100 |
To: | bug-Config-Any [...] rt.cpan.org |
From: | Mario Domgoergen <dom [...] math.uni-bonn.de> |
Hello,
i'm subclassing Config::Any to merge configuration variables
from differant files. I named my Module Config::Any::Merge,
but as Config::Any::finder uses __PACKAGE__ as search_path for
Module::Pluggable::Object::new my module is found as possible plugin for
Config::any. Maybe it would be saner to use a special Config::Any::Plugin
namespace for the plugins. Neither choosing a differant namespace like
ConfigAny::Merge nor overloading finder (that's what i'm doing in the
moment) seems to be the right choice for me.
Best regards,
Mario Domgoergen
--
Mario Domgoergen - Systemadministration
Mathematische Institut der Universitaet Bonn
Beringstrasse 4, 53115 Bonn / Zimmer 3
Tel.: +49-228-737773 / dom@math.uni-bonn.de