I think you're over-thinking this. If the warning is coming from their script and not from your module, it's their job to eliminate the warning. In their script they can do no warnings 'once';, or they can use the name twice.
Now, you could do something like this in your module:
sub import { warnings->unimport('once'); }
… which will effectively do no warnings 'once' on their behalf, but unimporting warnings for your caller is only something you should be doing if you document it in big red letters in your documentation.
"How does sort do it WRT $a and $b?"
Perl special cases the $a and $b package variables, not requiring them to be declared with our, and not warning about them being used only once. They're magic. Not as magic as other built-in variables, but still a little magic.
In reply to Re^3: How to suppress "only used once" regarding script file handles (that are in fact used in my module), but do it from a the module?
by tobyink
in thread How to suppress "only used once" regarding script file handles (that are in fact used in my module), but do it from a the module?
by hepcat72
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |