On Sunday 06 July 2003 4:06 pm, Jonathan Peterson wrote:
> The user could select back end like so:
>
> my $acme = Acme->new('DBI', {'dbname' => 'foo'..});
>
> And Acme would dynamically subclass as required.
From this I take it that you're wanting to play with @Acme::ISA at run time?
That would be bad as it would affect every instance, regardless of what
they were originally created from. I hope I've misread your plans and
that's not what you want to do.
What about having Acme::new() returning an instance of Acme::CSV,
Acme::HTTP, etc depending on the arguments/implementation. This does not
rely on inheritance by Acme. In fact, that's probably what you're planning
to do. Ignore my ramblings above. ... This sort of approach is a good idea,
IMO.
Ian
--
s&&@[EMAIL PROTECTED]@##@@#&&&y&^#@&712&&&($;='z')&&s&(..)&0$1&g&&s&$&0&&&s&(.)([^01])&
$1x$2&xge&&($.='a')&&s&$&d4823604df80d7e51d7018b9&&&(@_=$...$;)&&undef$.;do
{s&(.)(.*)(.)&$..=$1.$3,$2&e}while(length);s&&$.&;$*=0;undef$.;$..=($_?$_[(
$*+=$_)[EMAIL
PROTECTED]:$")foreach(map{hex}m&(..)&g);s&.*&$.$/&&&s&(\b.)&\U$1&go&&print
