Ah... you are right about confused, but I question your usage of highly. I.e.:
our $mp = __PACKAGE__->Data::Vars::new();
Now on to the next problem.
You see, this is a 6 year old program that I've been trying to modernize and re-factor over time. At one point everything was in MyBigOne::TorClient -- and it was unmaintainable spaghetti with little ability for extension.
I needed it to be extensible, Talk to multiple TorClients, Multiple Trackers Multiple TID's... Multiple and different instances of each type of object.
Anyway, as 1 module, it was a mess. Switch parsing was done manually, was a mess. So I started trying to break things into logical boundaries... This code was so old it used almost none of my newer routines that simplify things.
But when you mentioned DV -- I thought it shouldn't even be trying to go there...why? Cuz it wasn't called via the parent-module name.
Sigh. Thanks!In reply to Re^4: mro's which to use for flexibility?
by perl-diddler
in thread mro's which to use for flexibility?
by perl-diddler
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |