in reply to Perl Factory Method Pattern?

... and I would like to minimize external dependencies.

That is a feeling that many share, but I don't think it is worthwhile. CPAN exists so that the mainline distribution of Perl doesn't bloat to 10G, 90% any given user will not need. Most of the applications you can think of in Perl require at least 10-20% of their module code to be downloaded from CPAN. For example, one of the most downloaded module from CPAN is DBI. If CGI wasn't in the mainline, it would be the most downloaded module.

Download Class::Factory and just deal with it. CPAN isn't an external dependency - it's one of the primary reasons Perl is worth using.

Being right, does not endow the right to be rude; politeness costs nothing.
Being unknowing, is not the same as being stupid.
Expressing a contrary opinion, whether to the individual or the group, is more often a sign of deeper thought than of cantankerous belligerence.
Do not mistake your goals as the only goals; your opinion as the only opinion; your confidence as correctness. Saying you know better is not the same as explaining you know better.

Replies are listed 'Best First'.
Re^2: Perl Factory Method Pattern?
by pg (Canon) on Oct 11, 2004 at 20:02 UTC

    I agree that one has to deal with CPAN more or less, but it is quite normal to have concerns over quality.

    A mudule like DBI, as you said, is one of the most downloaded module. What does that mean? that means that it gets a better chance to have bugs found, and fixed because of all the attention it attracted. This creates a positive cycle, it is getting better, so more poeple use it; more people use it, so it gets even better...

    I am not sure about Class::Factory, but in general, it is always a good idea to ask for others' experience with a CPAN module before you use it, or the other way around, try it, and share your good or bad experience with others.