Personally I see no reason why turning warnings off makes sense. If the code is well written it shouldnt generate warnings under any circumstances. And if it does then probably both the user and you will want to know about them.

Furthermore if you are writing modules for others to use then why not use warnings::register and the functionality it provides.

package Foo;
use warnings;
use warnings::register;
sub some_func{
   warnings::warnif("some_func");
   print "some_func() doesnt do much right now....\n";
}
package main;
no warnings;
Foo::some_func();
use warnings;
Foo::some_func();
__END__
some_func() doesnt do much right now....
some_func at C:\Temp\warnings.pl line 12
some_func() doesnt do much right now....
[download]

That way the end user can decide if they want your code to generate warnings or not. (I realize this only applies to warnings explicitly generated by your code...)

---
demerphq
my friends call me, usually because I'm late....