On Thu, Dec 09, 2004 at 11:53:30AM +0000, Nicholas Clark wrote:
> On Wed, Dec 08, 2004 at 11:58:57PM -0500, Michael G Schwern wrote:
>
> > require Config; import Config;
> > if ($Config{'extensions'} !~ /\bData\/Dumper\b/) {
>
> For backwards compatibility reasons we can't change the "extensions" key,
> but it struck me a while back that it would be good if Config; could
> build and provide a nice hash keyed by extension name to avoid all that
> fandango anywhere.
>
> I'm not exactly sure of the most flexible way of doing this - maybe key
> by Module::Name, with a value of 'dynamic', 'static' or 'non_xs'
>
> Maybe it should be a separate module. Given that it can build this data
> from existing %Config::Config data it could go on CPAN and anything else
> could have it as a prerequisite.
Except then the module needing to check for optional prerequisites would
need that new module as a non-optional prerequisite and which point its
just a hell of a lot easier to do the regex dance above or just make the
optional module non-optional.
For a separate module to be useful for the purposes of checking for other
modules it would have to be in the core.
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern/
Global communism.
