in reply to Re: lazily getting around an Exporter problem
in thread lazily getting around an Exporter problem
Thankee, but I don't think these are the approaches for me.
The first, manually changing the module means I can't update it from CPAN anymore without having to reapply my changes. As the App I'm working on is deployed on multiple boxes, this isn't a solution that would we welcomed into the deployment process. It would also break any other modules that depend on it. I suppose I could RENAME the module to something else and do as you say to avoid the dependency problem, but I'd still be stuck manually caring for the module should it be patched.
The second is problematic as well. I need the function I'm doing to be in the same namespace as it's an OO module and needs access to $self. I could manually pass $self into the function, but it wouldn't be a particularly good way out of this problem.
Many thanks for the suggestions though.
meraxes