New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't block exporter with use_ok #41
Comments
Thanks for the work. I'm disinclined towards the special undef syntax. It would cause odd behavior should you do What would be nice is a doc patch to |
require_ok doesn't call import. doesn't import get called with use $module ()? |
No, that's the whole point of the empty parens. From
|
my bad. Stupid patch then. I'll send you a doc patch in thanks for you pointing out my stupidity. |
A pull request has been sent. it should just be a cherry-pick of sha 5be859f |
Done and in 0.97_01. |
I've got a unit test that parses for all my modules in a LARGE project and does a use_ok($module) on them. The problem is that some of the modules (legacy) export the same methods.
What I would like to do is to have use_ok do a "use module ()" this is not possible at present.
What I'm envisioning is this syntax, which should be meaningless in all other contexts: use_ok($module, undef) causes use $module ();
I've attached a patch for this. I'll provide tests if you're willing to accept the patch.
The text was updated successfully, but these errors were encountered: